Claude CodeCut over a 45-million-message alerting system with Claude Code and an operator go
Kaizen (Ashish Tonse, Oct 6, 2026) moved a nine-year-old alerting system that had sent/received 45 million messages onto their main platform with Claude Code running a 61-step runbook.
A prompt to try
Fill in the blanks. The prompt rewrites itself.
You are running our cutover from this runbook page. For each step: 1. Restate the command and expected output. 2. If the step is GO, wait for my explicit “go”. 3. Run it, compare output, write pass/fail + raw output to the dashboard. 4. On mismatch: stop, propose a fix, wait. Start at step 1. Never skip a GO.
Fill in anything in [brackets] before you send it. Anything that spends money, sends a message or signs something should stay behind your own approval.
How it went, step by step
- 01Put every step on one page: command, expected output, failure action, GO or not.
- 02Dry-run until mismatches become runbook fixes, not surprises.
- 03On the day: Claude runs reads alone; waits for the operator on writes.
- 04Log each result to a shared dashboard before the next step.
More like this
Grok BotKeep an 'on-deck' sheet of Grok Bot templates and review it weekly
@gambrill (Oct 15) keeps seeing Grok Bot templates they want to add, so they asked Grok Bot to build an "on-deck circle": a Google Sheet listing each bot template, its link and what it does.
Answer the messages a support bot missed during a server outage, then switch the catch-up off
Freelance automation developer Dmitry Prozorovsky runs an n8n-based AI support bot for a motorcycle-gear shop's VK community.
Grok BotHave Grok Bot check your email every 15 minutes and draft replies in your voice
Isaiah Crossman has their Grok Bot check their email every 15 minutes and draft a reply to anything that needs one.