How I run 10 Claude Code agents overnight and wake up to PRs — my parallel agent workflow

Showcase

I've been running Claude Code agents in parallel for the past few months and wanted to share the workflow that's been working for me. This isn't a product pitch — just a workflow walkthrough with the tools I use.

The setup

  • Machine: M3 MacBook Pro (works fine on 16GB, I have 36GB)
  • Orchestrator: amux (open source, Python + tmux)
  • Plan: Claude Code Max ($200/mo — unlimited, so 10 agents cost the same as 1)
  • Isolation: git worktrees (one per agent, no conflicts)

The workflow

Evening (30 min):

  1. Look at my backlog and pick 10 tasks that are independent
  2. Write a 5-line spec for each: goal, constraints, acceptance criteria
  3. Push specs to the amux kanban board
  4. Run amux start-all — 10 sessions spin up, each claims a task
  5. Close my laptop

Morning (45 min):

  1. Check the amux dashboard from my phone (it's a PWA)
  2. Usually 8/10 sessions completed successfully, 1-2 hit edge cases
  3. Review each agent's branch, quick sanity check
  4. Merge the clean ones, fix the edge cases manually

What makes it work

Git worktrees are essential. Each agent gets its own copy of the repo via git worktree. No file conflicts, standard git merging. Without this, agents step on each other constantly.

Self-healing watchdog. Claude Code crashes sometimes — context overflow, API rate limits, stalled responses. amux's watchdog detects this and auto-restarts the session with the last prompt. Without this, I'd wake up to 3 crashed sessions every morning.

Atomic task claiming. The board uses SQLite CAS (compare-and-swap) so two agents never grab the same task. Sounds like a small thing until you waste 2 hours of compute on duplicate work.

Tight specs. The single biggest factor in agent quality isn't the model — it's the spec. A 5-line spec with clear acceptance criteria produces better output than a paragraph of vague instructions with Opus.

What I've shipped this way

  • Migrated 50 JS files to TypeScript (8 agents, 1 night)
  • Expanded test coverage from 40% to 78% (10 agents, 1 afternoon)
  • Built 12 API endpoints for a new service (6 agents, 3 hours)
  • Cleared a 15-bug backlog (10 agents, 2 hours)

Tools

Happy to answer questions about the workflow. What's your setup for running multiple agents?

Posted Apr 10, 2026, 12:55 AM UTC

914
Loading comments…