A day about bots finding money, and about what breaks when you can't see what they are doing. Two small businesses put numbers on savings, a trucker shipped fixes from the road, and several users hit walls they had no warning about.
01
// build, small business
Thirty minutes in, the bot found $6,000 in unbilled jobs
3 jobs, over $6,000
A staff software engineer set up Grok Bot at a small business with read access to internal Slack, the main customer inbox, the jobs calendar, the team's Google Sheets and QuickBooks Online in read-only mode. Within 30 minutes it found 3 jobs the team forgot to invoice, worth over $6,000. Separately, a property management broker says a bot going through company expenses has cut about $300 a month.
A log trucker built his paperwork app between loads
GPS 170 miles short, fixed
A log truck driver who had never written code built Haul Sheet, an iPhone app for the family's 2 trucks, from his phone with Grok Bot. It does weekly time cards, scans logger and mill tickets, splits miles by state from GPS, tracks fuel, and makes invoices and profit and loss. He tests it in the truck and sends screenshots of what breaks: GPS came up 170 miles short, a ticket date was misread, and there is no signal in the woods, so scans now save offline.
The bots stopped, and the only clue was the usage page
stopped at 85% usage
A writer and builder says their Grok Bots suddenly stopped working, and it turned out they had burned through their usage with no warning. Another user says a bot stopped mid-task at 85% usage, and the usage screen then failed to load. A user running a coordinator bot, five topic bots and a weekday summary across 4 Gmail accounts says all they can see is one weekly percentage, and asks for usage by bot, by routine and by task, plus an alert at 80%.
The home tunnel dropped and the bot quietly changed IPs
down 15 minutes
A user on the $100 plan routes bot traffic through their own PC. On Oct 20 the tunnel dropped when Clash Verge restarted on the PC, stayed down for 15 minutes, and the bot silently switched back to the default IP. It only came back when they toggled the "Route traffic through this computer" switch off and on themselves. Support confirmed it is a known bug.
A user running 28 Grok Bots on one shared computer points out that they all share one identity, so the separation between them is rule-based, not enforced. Their workaround is per-agent users, sandboxes and audit logs, and they filed a request for native per-agent identity. Another builder keeps their bots in line from outside: Claude Code wrote each bot a rules file and set up a webhook to check on them when they start to drift, and on the third attempt the setup stuck.