Run parallel coding agents from Markdown specs in tmux
According to the write-up, 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. He covers 4–8 agents at once, and has written 300+ specs in one project.
- Agent or tool
- Claude Code
- Topic
- Software Development
- Reported on
- Hacker News
- Added
- 2026-10-15
Why it matters
Coding agents are moving from autocomplete to doing whole tasks: reading a codebase, making a plan and changing many files. This case is a concrete example of where that works in practice. It is one of 106 sightings filed under Software Development on Agent Sightings (number 38 by interest), and one of 164 involving Claude Code.
How you could try it
Here is a reusable prompt, written by us in our own words, that captures the task. Paste it into Claude Code or any similar agent and adjust the details to your situation.
In this repo, run parallel coding agents from Markdown specs in tmux. Read relevant code, apply a minimal patch, run available checks, and summarize the diff. Stop before merge or deploy.
The prompt breaks down into 3 steps you can check as the agent works:
- In this repo, run parallel coding agents from Markdown specs in tmux.
- Read relevant code, apply a minimal patch, run available checks, and summarize the diff.
- Stop before merge or deploy.
Tip: Work on a fresh branch, ask for a plan before edits, and review the diff and test results before merging.
Source
Read the original first-hand account on Hacker News: https://news.ycombinator.com/item?id=47218318. Our summary is a paraphrase; details are in the source.