The Claw Loop
One prompt. Autonomous development.
Version 2.0 — February 12, 2026
The Claw Loop turns your Clawdbot into a supervisor that drives Claude Code through entire development sprints — creating stories, writing code, reviewing its own work, and moving to the next task. All while reporting progress to your phone every 3 minutes.
It works with BMAD Method, GSD, or any custom slash command workflow. Copy the prompt, paste it to your Clawdbot, answer a few setup questions, and walk away.
How it works
- Your Clawdbot launches Claude Code in a tmux terminal session
- A cron job wakes your bot every 3 minutes to check on progress
- When Claude Code finishes a step, your bot clears context and sends the next command
- You get a short status update on your phone after every check
- Crashes, stalls, and context limits are handled automatically
The key insight: Claude Code is powerful but not autonomous. It finishes a task and waits. It hits context limits and stalls. The Claw Loop bridges that gap — your Clawdbot becomes the factory floor supervisor that keeps the machine running.
Version History
The Claw Loop prompt evolves as we learn what works. Each version is documented and downloadable.
- •Replaced kill+restart with /clear between steps (per Anthropic official docs — Boris Cherny recommends clearing context, not compacting)
- •Added model switching: Opus 4.6 for planning & code review, Sonnet 4.5 for development
- •Added story numbers in slash commands (e.g., /bmad-bmm-dev-story 8.1)
- •Added YOLO/option responses to decision logic ([a] [c] [p] [y] prompt handling)
- •New section: Why /clear instead of kill+restart (saves ~10 seconds per transition, slash commands stay loaded)
- •Context overflow threshold changed from 100% to 90%+ for earlier intervention
- •Status reports now include current model (Opus/Sonnet)
- •GSD step transitions updated to use /clear instead of kill+restart
- •Initial release with BMAD Method support
- •GSD Method support and custom workflow option
- •Core cron-based orchestration loop (3-minute heartbeat)
- •tmux session management with kill+restart between steps
- •State file (JSON) for persistence across cron fires
- •Automatic crash recovery and context overflow handling
- •Multi-channel status reporting (Telegram, Discord, Signal, etc.)