Grok Bot use cases that involve GitHub, as described by their authors. 5 so far.
One scout bot reads X on Monday; other bots wake on file changes to score the idea, open a PR and draft a deck.
Schedule: Monday 09:00 + file triggers
Setup: One clock (Monday 09:00) for the scout; every other bot triggers on a new line in LEDGER.md; spends and posts go through approval. Author reports dropping from 1,176 to about 60 runs a week.
Turns the X feed and bookmarks into EPUBs with a morning summary, stored in a private repo.
Schedule: Every morning
Setup: Everything is kept in a private Git repo as a personal library.
A chief of staff for client priorities plus bots for production monitoring, data takedowns, inbox cleanup and Linear triage.
Schedule: Daily / weekly
Setup: Chief of staff reads Slack, Linear, GitHub, Gmail, Calendar and Notion; a monitor watches Vercel logs, the database, GitHub and support email; a privacy guard re-checks takedowns weekly; others triage spam, LinkedIn DMs, iMessage and physical mail via Earth Class Mail's MCP.
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.