Andrew (@Ra3orbladez) shipped Swarm v0.14.0: it no longer only watches agents—it can steer them. With on_stop=block, when Claude Code finishes a turn in a claimed worktree Swarm runs required repo gates first; on failure it refuses stop and returns the gate name plus output tail (max three refusals, then an incident to avoid burning budget). Permission prompts surface on the dashboard with Allow/Deny, co-editing agents learn of each other’s file edits immediately, idle sessions wake on message, and rules can rewrite commands (e.g. strip git commit --no-verify). Setup: bunx @ra3orblade/swarm setup.

Key Takeaways

  • ✓on_stop=block runs repo gates before Claude Code can stop; red gates refuse stop with feedback (max three).
  • ✓Dashboard Allow/Deny for permission prompts; cross-agent file-edit awareness; idle sessions wake on message.
  • ✓Rules can rewrite commands (e.g. strip --no-verify); install via bunx @ra3orblade/swarm setup.
⚡

Key Decision Metrics at a Glance

TL;DR Verdict
🏆 Benchmark RankRank
No model benchmark in this story · see current rankings
Full Leaderboard→
💰 Cost & PlansCompare
API & Subscription
Compare Plans↗
🛠️ Ecosystem & IDERules
Claude Code (Anthropic)
Setup IDE Rules↗
🧭

Heavy Claude Code use: compare subscription limits and API bills

Compare 40 dev plans & simulate token costs vs $20/mo subscriptions

⚔️ Compare Model→💰 Compare plans & limits↗
Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.

⚔️ Launch VS Compare→💳 View Plans↗
Up NextClaude Code 2.1.304 adds guided /auto-mode-setup and warns Pro/Max users before resuming an inactive conversation would eat into the 5-hour usage limit
Read Now→