Real Grok Bot use cases for coding, with how each bot is set up. 7 so far.
When Cursor cloud agents hit a usage limit, the bot built on its own computer and kept scheduled posts on time.
Schedule: Scheduled
Setup: News posts and two guide rewrites still went live on schedule.
Shipped a load-as-you-scroll change, caught a scroll bug with its live check, rolled back, then reshipped the fix with a regression test.
Setup: Timeline from the author: shipped at 11:37 pm, live check caught the bug and rolled back at 11:41, reshipped with the fix and a regression test at 11:51.
A bot fleet updates a local Command Hub with an open-questions queue, a bookmark radar, an API explorer and a board game picker.
Schedule: Nightly
Setup: Overnight sprints drop multiple-choice cards into an Open Questions tab; a nightly script links X bookmarks with an Obsidian vault and sends picks to Notion; health checks and Pi-hole stats run on OS timers with no LLM tokens; a Friday routine ships one surprise project.
A Bash script runs the server checks; the bot reads its one-line result each morning and stops if it says OK.
Schedule: Every morning
Setup: Replaced a long morning checklist run by the bot with a 200-line script to save usage.
Grok Bot messages Claude Code via its CLI, and Claude Code can message back.
Setup: Author says you can ask the bot to set it up.
Claude Code runs on the bot's own computer, and bot project managers direct it from GitHub issues.
Setup: Author logged into Claude Code on the Grok Bot computer.
A coordinator, a Linear PM, a builder, marketing, sales, ideas, tech news and a morning security review of commits.
Schedule: Mornings and evenings
Setup: PM fleshes out Linear issues; builder picks up Todo issues after agreeing the approach; ideas are logged in Notion. Every routine only looks at what's new since its last run.