1. Charged Twice, Refunded Plus a Discount Without Making a Call: Grok Bot Phoned Support, Got Past Their AI and Talked to a Human

After a grocery order charged him twice, he gave his Grok Bot one task: call support and fix it. The store's AI answered first, his bot named the order number and explained the double charge, and the call was handed to a person. The human approved the refund, apologized and added a discount on his next order. He wasn't on the call at all. The same day he also had Grok Bot call him as a morning alarm and plan the week's menu.

2. A Log Watcher Instead of Hours of Senior Dev Time: Headless Claude Code Reads a Startup's Logs on a Schedule and Pings Slack Only When Something Needs Action

A founder piped all of his product's logs into an S3 bucket with 90-day expiry, made them queryable with SQL through AWS Athena, and connected a server running headless Claude Code on a schedule with skills. Now it analyzes everything happening in the product and posts in Slack only when there is something to act on. He says this used to take a senior developer hours a week, and the setup took him about 7 hours in one day.

3. A Homelab Bot Named Rack: Grok Bot Handles Maintenance, Config and Software Setup Across His Machines and Saves Him Several Hours a Week

A homelab owner with several machines and environments had his main Grok Bot create a dedicated bot, named Rack, to manage the infrastructure. It handles general maintenance, configuration and setting up new software, and he says it saves him several hours a week. He notes it needs Grok Bot installed on a desktop computer so it can reach the machines.

4. 40 Anime Episodes in 2 Weeks With One Fixed Cast, Top Episode 651K Views: A Creator Packed the Whole Workflow Into a Free Skill for Claude Code and Codex

A creator made 40 anime episodes for Instagram in two weeks with the same characters, and their top episodes reached 651K, 546K and 346K views. They turned the workflow into an open-source agent skill for Claude Code or Codex. A series file keeps the cast, art style and voices consistent, the agent pitches three hooks first, writes a shot-by-shot script, quotes the generation cost and waits for a yes, makes one test clip before the rest, then edits, checks and writes the cover and caption. It logs each episode's views to rank future premises.

5. 286,522 Input Tokens Down to 196,983: A Team Cut Its AI Agent's Token Bill About 31% and Published What Worked and What Broke

A team running an AI business intelligence agent found it re-read 17,000 tokens of instructions and tool manuals before every thought. They measured first with an open-source bench and quality checks, then made cuts in order: removing 10 tools the agent never called, shortening old tool results but never the current turn, ordering prompts so they cache, and adding a grouped query so the model asks once instead of five times. That last change cut one real question by 41%. A three-question conversation dropped from 286,522 to 196,983 input tokens, and they also list what failed.

Charged Twice, Refunded Plus a Discount Without Making a Call: Grok Bot Phoned Support, Got Past Their AI and Talked to a Human

Copy this and paste it into Grok Bot:

I was charged twice for the same order from [store]. Order number: [number], date: [date], amount: [amount], last 4 of the card: [digits]. Call their customer support for me and get the duplicate charge refunded. Be polite and brief: give the order number, explain it was charged twice, and ask for a refund of the duplicate. If an automated assistant answers, ask to be transferred to a person. Don't agree to store credit instead of a refund, and don't share any card or account details beyond what I gave you. When the call ends, tell me exactly what they agreed to, any reference number, and when the refund should show up.