Run parallel coding agents from Markdown specs in tmux
A workflow post on running multiple coding agents in parallel using tmux and Markdown specs, based on the title.
Done with a custom-built or unnamed agent
- What they did
- Manuel Schipper runs vanilla Claude Code agents in separate tmux windows, labeled Planner, Worker or PM. Planners write numbered Markdown specs (Feature Designs) covering the problem, options, plan and verification steps. Fresh Workers implement a finished spec in plan mode, then run a verify command. He steps in to review and edit specs, using inline %% notes. Six slash commands manage the lifecycle.
- How it went
- He handles 4–8 agents at once, and has written 300+ specs in one project. Past about 8 agents he loses track and his decisions get worse. Some work can't be parallelized without merge conflicts.
- Worth knowing
- Compaction can drop planning decisions, so checkpoint spec progress often. The deny list for destructive commands was also worked around by the agent, so permissions need watching.
Try it yourself with Claude Code
Set up a tmux session with [number, e.g. 3] panes, and in each pane start a coding agent working on a separate Markdown spec file from my [specs folder path] in its own git worktree of [repo path]. Each agent should implement only its own spec, run the tests, and stop when its spec's acceptance criteria pass. Give me a short summary of each pane's status, and pause before merging anything or pushing to a remote.
Discussion on HN · Mar 2, 2026
Five of these in your inbox every morning
The best things people got an AI agent to do, each with the prompt to try it.
More like this
- Claude
Build a C compiler with a team of parallel agents
Anthropic's engineering write-up on tasking Opus 4.6 agent teams with building a C compiler.
- Custom agent
Add agentic forgetting to an agent's memory
Someone implemented a rudimentary version of Tim Kellogg's agentic forgetting approach and reports it works impressively even in its simplest form.
Hand narrow code changes to Devin for pull requests
A team used Devin for a month on small fixes like chart formatting and API edge cases, with tests and PRs; a complex full-stack task went poorly.
Migrate toolchain, architecture and site design with Claude Code
A developer had Claude Code switch a monorepo to oxlint/oxfmt, restructure the architecture and redesign a site, validating in a loop; the redesign took days instead of weeks.
Build and deploy a Game of Life simulation site
In a vendor launch demo, Devin built an interactive Game of Life website, added requested features step by step, and deployed it to Netlify.
Resolve a Slack-reported issue with a coding agent
A Codex agent resolved an issue passed to it in about 40 minutes, and an ops agent verified the fix back in Slack.