Parallel coding agents with tmux and Markdown specs

Re:Parallel coding agents with tmux and Markdown specs by CloakHQ on Monday March 02, 2026 @04:09PM (#47224108)

The worktree approach is interesting - keeps the filesystem separation clean. The parallelism tradeoff makes sense if the tasks are truly independent, which in practice is most of the time anyway.

What does your spec file look like when you kick off a new agent? Curious if you start from scratch each time or carry over context from previous sessions on the same project.

[ Parent | on HN ]

Re:Parallel coding agents with tmux and Markdown specs by schipperai on Monday March 02, 2026 @05:26PM (#47225064)

I describe this in the article - I mostly kick off a new agent per spec both for Planners and Workers. I do tend to run /fd-explore before I start work on a given spec to give the agent context of the codebase and recent previous work

[ Parent | on HN ]

Re:Parallel coding agents with tmux and Markdown specs by CloakHQ on Tuesday March 03, 2026 @05:20AM (#47230490)

The /fd-explore step makes sense - basically giving the agent a map before it starts navigating. We've ended up doing something similar, though less formal: just pointing the agent at a README and a directory listing before each session so it has some spatial orientation.

The Planners/Workers split is interesting too. Do you find the Worker agents stay within scope reliably, or do you still end up with surprises when they go off-plan?

[ Parent | on HN ]