Coordinating parallel agents (worktrees, merge conflicts)

At some point, keeping track of the agents became a problem of its own. I kept forgetting which agent was working on which branch/worktree, which sessions were waiting for me, and which changes I still needed to review among the many chats I have open.

lcx · Nov 2, 2026 · comment in “Repobs – A local dashboard to manage agent worktrees and branches”

For me the answer to painful merge conflicts has been...

anentropic · Nov 2, 2026 · comment in “Show HN: OmniDiff – Opensource, super fast, content aware Git difftool, in Rust”

I’ve been using JetBrains IDEs for over a decade but rarely open them anymore because working on several worktrees concurrently is extremely frustrating and wasteful.

dr_faustus · Oct 25, 2026 · comment in “JetBrains Thinkrail”

My attempts at finding a middle ground: * I use LLMs to resolve the more annoying merge conflicts.

perlgeek · Oct 20, 2026 · comment in “Ask HN: How to deal with shipping AI-written code you don't understand?”

There's a new project called kache https://github.com/kunobi-ninja/kache that takes this even further and handles more edge cases with worktrees, but it's newer. If you were pulling the entire project fresh and rebuilding everything in every worktree all the time without any caching then it would be frustrating.

Aurornis · Oct 1, 2026 · comment in “How to speed up the Rust compiler in September 2026”

The managers who knew how the system worked had no idea about the actual code underneath it all because it was abstracted away from them through multiple layers of hierarchy. The actual code which was mostly written by 21 or 22 year olds who largely had no idea what was going on other than the fact they had to make it work or risk the ire of higher ups was a mess, unless the consultant orchestrating it all had real …

forger2001 · Sep 28, 2026 · comment in “The problem is not AI code, but not knowing about system architecture or intent”

Given this, I kept coming back to Sol 5.6 as my daily driver (with consultations from Fable and Astra when available). Sol has an autistic character that smells like RL deepfry, which can be annoying, but it is nonetheless predictable, communicates more plainly than Claude, and is good at code and orchestration.

schipperai · Sep 22, 2026 · comment in “Claude Opus 5.5”

I mostly use IDEA now to navigate/review the code or do my own debugging/tracing. My time in the IDE has fallen drastically which is why the high ram/cpu usage when I’m not even “using” the ide are so frustrating, especially since I’ve excluded the nested worktrees parent folder (.claude/worktrees).

joshstrange · Sep 22, 2026 · comment in “JetBrains Air: A System of Products for Agentic Software Development”

At, GPTree, we run several coding agents across our team on one repo using parallel worktrees. Apart from wasted time reviewing and fixing conflicts at PR time, the failures that hurt the most are when multiple plans or tickets cause architecture changes that cannot both be true.

naw103 · Sep 21, 2026 · story in “Show HN: Foremerge – Catch intent conflicts between parallel coding agents”

Then prunes them and removes local branch pointers if they match the remote ones. These all are handwritten and probably buggy, but still less prone to errors than typing out `git worktree add -b foo-123-fix-missing-semicolon foo-123-fix-missing-semicolon origin/develop` manually every time.

anilakar · Sep 11, 2026 · comment in “Working with Git Worktrees in Magit”

We're trying to move some of our services within the Internet Archive's kubernetes cluster and we've done a great job migrating towards a world where everything is dockerized. It used to be a very painful process for our team of 3 to handle server ops, upgrades, and networking for nearly 15 manually orchestrated servers.

mekarpeles · Sep 10, 2026 · comment in “Keep Our Servers Running”

We're building the fix. You'll own the intelligence layer: LLM-powered agentic workflows (tool use, structured outputs, multi-step orchestration), RAG/retrieval pipelines, lightweight ML for classification/ranking/entity matching, and evaluation loops for hallucination risk and output quality.

konstantinmuell · Sep 1, 2026 · comment in “Ask HN: Who is hiring? (September 2026)”

Sadly doesn't work with git worktrees at all.

binarin · Aug 31, 2026 · comment in “Maiao: Gerrit-style code review workflow for GitHub, GitLab, Gitea, others”

"Well, just do it yourself", "write code by hand" - I heard you scream from your chairs. I wish I could, but after 10 hours and 15 parallel agents, I no longer have the brain capacity to do anything.

fnoef · Aug 27, 2026 · story in “Tell HN: Man, AI is killing my brain”

It’s like “helping another team managing their work stream” experience rather than coding yourself. Funny enough models seem to have personalities and the dis on each other - when I had an opus orchestrator dispatching fable workers, they would comment on how “unreliable” it was and it had “evidence to prove it” and fable thinks opus is too rigid and needs more hand holding… it really starts to feel like managing te…

seer · Aug 18, 2026 · comment in “AI;DR (AI; Didn't Read)”

While I was excited to try out the seamless Codex wrapper, this leakage was unacceptable compared to a ZDR OpenRouter provider like fireworks. Where I struggle is now in architecting a clean way to have Hermes separate out personal stuff from coding stuff, and then orchestrate coding through Codex as that seems to be the only way to use it headlessly on my phone since they have no way of doing that in the ChatGPT ap…

shostack · Aug 13, 2026 · comment in “My Agent Setup”

Very often, when I'm running Claude in manual review mode, it will attempt to do things which are not "dangerous" but are misaligned with what I want it to do. Maybe I'm fighting the model here but for example, when orchestrating other agents to do work, Claude really badly wants to be overly prescriptive about how the work gets done, telling them exactly which files to edit, exactly what not to do, etc. instead of …

dgunay · Aug 10, 2026 · comment in “Auto mode is now the default in Claude Code”

Rule of thumb: worktree for "don't let agents collide", container for "don't let an agent hurt the host". Most local setups only need the first, and people tend to reach for heavyweight sandboxing before they need it, then abandon it because it's painful.

krupkinmaxim · Aug 9, 2026 · comment in “OpenChamber: An Agentic Development Environment”

Keeping a heavy IDE open, waiting for it to load, and then opening yet another terminal tab just to run an agent was more overhead than it was worth. It got worse with multiple agents — one terminal per agent, and my desktop turned into a mess of windows.

asdsa112 · Aug 3, 2026 · story in “Show HN: AgentCodeGUI – Multi-Account Desktop GUI for Claude Code and Codex”

Next time you commit, that runs on your machine as you. Separate thing - worktrees just get annoying to manage.

alchaplinsky · Jul 30, 2026 · comment in “Git worktrees are not an isolation boundary for coding agents”

I recently went back to using my terminal more instead of using tools like Conductor, Paseo, Codex App. This led me to start managing my own worktrees, which is annoying if you want to set up your whole environment in a worktree.

kasktra · Jul 30, 2026 · comment in “Show HN: I built myself the simplest worktree management tool”

Show HN: Argus – VSCode Worktree Agent Session Manager Running parallel Claude Code/Codex agents across worktrees in vscode is annoying.

pdcd · Jul 26, 2026 · story in “Show HN: Argus – VSCode Worktree Agent Session Manager”

I'm building CobaltCode, a platform for running coding agents inside persistent development environments. Basically I was fed up with git worktrees and having to run everything locally, usually one at a time so built CobaltCode.ai.

vpetroff · Jul 23, 2026 · story in “Show HN: CobaltCode – Dedicated persistent computer for Codex”

Ask HN: Agentic Coding for Messy Multirepos? My job has quite an annoying "dev" environment setup, with a slew of scripts, a shared library that works as interface for different services. the shared library and all services live in separate repos. worktrees have worked sort of, but i need to be careful to break things down in a way that no two agents are modifying db schema at the same time, since they share resourc…

pseudolemon · Jul 22, 2026 · story in “Ask HN: Agentic Coding for Messy Multirepos?”

With the scaffolding you could probably get this to work okay enough even with a weaker model. On the orchestration side, Claude could help answer what good porting practices would be but it doesn't just get there itself, it requires hours of someone who understands the context of the project from bottom up and a clear understanding of what will/won't work to get the right scaffolding to do the job well.

zamadatix · Jul 9, 2026 · comment in “Rewriting Bun in Rust”

Show HN: NT – fly around Git worktrees from your shell Got tired of fighting git worktrees, so I made nt (navigate tree).

Allisonmahmood · Jun 26, 2026 · story in “Show HN: NT – fly around Git worktrees from your shell”

agent orchestration will be painful if you still have to babysit context.

dasubhajit · Jun 23, 2026 · comment in “[dead]”

Especially if you have certain stack based workflows. Worktrees are kinda half solution here but depending on the repo type and if you are dealing with LFS or sparse checkouts, I've had agents struggle really hard to work through a stack or rebase things without a lot of thrashing or being IO bound by just stumbling into operations in a boneheaded way.

zbowling · Jun 22, 2026 · comment in “Show HN: Oak – Git alternative designed for agents”

I keep using it for specific Node versions and the integration with fnox. The big drawback: having Claude complain every couple of hours that the new worktree is untrusted; or having to prefix a bunch of commands with `mise exec …` is annoying as well.

port11 · Jun 12, 2026 · comment in “Show HN: Homebrew 6.0.0”

For orchestration I gave pi-subagents a try, and didn't care for it, ended up with hung agents sticking around forever and I wasn't even doing anything terribly fancy. Claude's subagent control is annoying and clumsy, but it works.

chuckadams · Jun 10, 2026 · comment in “Apache Burr: Build reliable AI agents and applications”

Do you guys think that there will still be some work that is done locally vs the cloud, how are you thinking about the split from what you've seen developers doing? I also agree with the fact that git worktrees can be super frustrating to manage especially across multiple agent sessions.

lavaman131 · Jun 6, 2026 · comment in “Show HN: Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud”

Cursor seems to pretty much have all the available tools there already (it can already spawn agents to their own worktrees with proper setup scripts, for example). I don't get why they don't do it and instead insist on a buggy and confusing agents experience.

jorl17 · May 22, 2026 · comment in “Open source Kanban desktop app that runs parallel agents on every card”

And suddenly to have a Postgres cluster you need Kubernetes, and Helm, but also need to know both PG config and the orchestrator's config, etc. It's a mess and the OpenBSD people somehow knew that decades before I did.

tete · May 19, 2026 · comment in “OpenBSD 7.9”

- Using LLMs in an agentic way will improve (git worktrees, sliced PRs, spec driven steps) So what happened here is a mess, but you gotta break a few eggs to make a souffle.

tomaytotomato · May 15, 2026 · comment in “Bun Rust rewrite: "codebase fails basic miri checks, allows for UB in safe rust"”

Electron on its own isn't that bad, and surely not responsible for GBs of RAM - the main bottleneck I'm facing when dealing with a dozen+ parallel tasks is that each claude code terminal eats up easily 200MB of RAM.

nokturn · May 11, 2026 · comment in “What do you NOT like about Cursor / VSCode / Claude Code desktop / Codex / etc.?”

- "X is cool but lacks worktrees support" - "I hate that I have to go to GitHub to check if my PR has been already approved"

nokturn · May 11, 2026 · story in “What do you NOT like about Cursor / VSCode / Claude Code desktop / Codex / etc.?”

I've been comparing Claude vs Codex using GPT and Claude consistently is better than GPT about reasoning, about writing code, and using the tools as appropriate. GPT for instance had a lot of issues using git worktrees, and didn't understand how to correctly use it to then merge stuff back into a main branch, vs Claude which seems to do this much more naturally.

X-Istence · May 9, 2026 · comment in “Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc”

I used a Conductor setup script that runs my local dev setup in each worktree. This didn't work because of port collisions between docker containers.

spmartin823 · May 1, 2026 · story in “Ask HN: How are people testing while using agent orchestrators?”

so I built jj-navi - a tiny rust based cli that makes jj workspace orchestration a lot less pain in the ass.

Sreenington · Apr 29, 2026 · story in “Show HN: Nv – workspace orchestrator for jj built for parallel agent workflows”

Last week I built Grove as the successor to my IDE. Like many, I suspect, I was struggling to coordinate multiple agents per repo recently.

sebasv_ · Apr 25, 2026 · comment in “Grove: A simple snappy TUI repo+worktree+shell manager”

I feel like we’re over-capitalizing a problem that could be solved with better protocols. If the "Git successor" is just a wrapper to help agents not hallucinate their own worktrees, it feels like a very expensive solution to a context-window management problem.

michaelashley29 · Apr 10, 2026 · comment in “We've raised $17M to build what comes after Git”

Interesting concept! But I'm struggling to understand what makes this strictly better than just having agents push to separate git branches and then having an orchestrator agent resolve the merge conflicts?

altaro8g · Apr 9, 2026 · comment in “Show HN: 8d – Agent-Native Version Control, where Git breaks”

Show HN: I built a local data lake for AI powered data engineering and analytics I got tired of the overhead required to run even a simple data analysis - cloud setup, ETL pipelines, orchestration, cost monitoring - so I built a fully local data-stack/IDE where I can write SQL/Py, run it, see results, and iterate quickly and interactively.

vpfaiz · Apr 8, 2026 · story in “Show HN: I built a local data lake for AI powered data engineering and analytics”

Happy to go deep on the architecture or the worktree strategy. For those running multiple agents: what's the biggest operational pain point?

Zedmor · Apr 4, 2026 · story in “Show HN: Batty – Run a team of AI coding agents in tmux with test gating”

The instructions for say, https://cursor.com/docs/configuration/worktrees are for the 3.0 version now, and the version 2 docs lack images in Wayback Machine. Is there a way to see the old docs if you haven't upgraded?

Noumenon72 · Apr 3, 2026 · comment in “Cursor 3”

I also don't enjoy the fact that I can't push a job to the web when I am leaving work. Worktrees aren't fun as I can't run the services on different ports that easily for testing, further managing different TMUXs is painful.

break_the_bank · Apr 2, 2026 · story in “Ask HN: What is your dev set up like?”

- visualJJ is the best worktree/workspace manager that no one is talking about, i wish it was open source but there is currently no alternative i am aware of

jFriedensreich · Apr 1, 2026 · comment in “Show HN: Baton – A desktop app for developing with AI agents”

Show HN: Castra – Strip orchestration rights from your LLMs I got tired of AI agents forgetting what they were doing the moment their context window filled.

amangsingh · Apr 1, 2026 · story in “Show HN: Castra – Strip orchestration rights from your LLMs”

Would love if there is a way to parallelize playwright mcp using multiple agents and such, but it seems it's a fundamental limitation of that MCP that only on instance/tab can be controlled. Chrome MCP is much slower and by default pretty much unusable because Claude seems to prefer to read state from screenshots.

silverwind · Mar 28, 2026 · comment in “Anatomy of the .claude/ folder”

Claude creates non-semantic plan names like "aquamarine-owl" that are trapped within a single agent context. Spinning up multiple agents to check on different aspects of a plan is annoying and slow, and managing terminal tabs is pure hell.

zdenham · Mar 27, 2026 · story in “Show HN: Anvil – Desktop App for Spec Driven Development”

And plenty of successful merges end up with code that won't compile. FWIW I've struggled to get AI tools to handle merge conflicts well (especially rebase) for the same underlying reason.

jwilliams · Mar 22, 2026 · comment in “The future of version control”

So I switched to git worktrees and ran 5–8 parallel cc sessions. At that point, my prompt typing speed became the real bottleneck — and Yak genuinely helped me ship Yak faster. ^_^

zonghao · Mar 15, 2026 · story in “Show HN: Yak – Voice typing tool in Tauri/Rust that auto-presses Enter for you”

PipeStep is specifically for debugging CI pipelines, not general LLM/flow orchestration. The target user is someone staring at a failing GitHub Actions run who's tired of the commit-push-wait-read-logs cycle.

photobombastic · Mar 13, 2026 · comment in “Show HN: PipeStep – Step-through debugger for GitHub Actions workflows”

agents on different devices can communicate and collaborate. No central orchestrator, which we all know doesn't work tbh...

DanielJLosey · Mar 13, 2026 · story in “Show HN: DarkMatter – P2P mesh networking protocol for AI agents”

Getting this to work declaratively rather than with imperative callbacks took several iterations. Our main bottleneck now is token limits rather than the orchestration.

frequencyai · Mar 10, 2026 · comment in “Frequency – autonomous agent pipelines coordinating through shared state”

But the real experiment here is how it was built. Instead of writing it all myself, I acted purely as the orchestrator for a 3-model AI team, using a strict Role-Based Access Control (AI RBAC) approach to eliminate context loss and hallucination:

edenwang233 · Mar 9, 2026 · story in “Show HN: I built a 38K-line Rust CLI using 3 AI models as my engineering team”

Managing it is not. Every tool I found was either another agent, an IDE plugin, an abstraction over my CLIs, or doesn't understand worktrees.

parsak · Mar 5, 2026 · story in “Is anyone else drowning in terminal tabs running AI coding agents?”

Show HN: Scape – One-click worktrees and orchestrators for Claude Code Hey HN, we've been using Claude Code daily for months, and built Scape to fix our biggest pain point: managing multiple worktrees quickly & reducing the mental load of switching between them quickly.

bgnm2000 · Mar 5, 2026 · story in “Show HN: Scape – One-click worktrees and orchestrators for Claude Code”

AI has made writing code 10x faster, but shipping is still painfully slow. The bottleneck has shifted downstream - to merge conflicts, flaky tests, inconsistent code quality, and dozens of other frictions that drain productivity and morale.

trunksuzieross · Mar 4, 2026 · comment in “Ask HN: Who is hiring? (March 2026)”

Multiple agents, one branch, one overwrites the other. Git worktrees give isolation but the per-session setup/teardown doesn't scale.

rchaz · Mar 2, 2026 · story in “Show HN: Git-stint – Built for AI coding agents to multitask without collisions”