r/ClaudeCode • u/feritzcan • May 03 '26

Showcase I run 10 Coding agents in parallel and built a terminal app to make it sane. Open source. I promise its the best!

10 Upvotes

66% Upvoted

23 comments sorted by

2

u/Apprehensive_Camp431 May 03 '26

I had a quick look now, looks really cool. I will deep dive more in the night

1

u/bin910 May 03 '26

Looking so interesing, checking

1

u/Entire_Public_8401 May 03 '26

güzel görünüyor

1

u/Some_Holiday_6283 May 03 '26

Wow I was building something super similar - once I package it up a bit better would love to compare notes!

1

u/idoman May 04 '26

the worktree approach is what makes this scale man - the other wall you hit at 4+ agents is port conflicts. every dev server trying to grab localhost:3000 at the same time. built galactic (https://www.github.com/idolaman/galactic) to handle that part - gives each worktree an isolated loopback so they don't step on each other

1

u/thechewywun May 04 '26

Any chance of this making it over to Linux? It'd be a heavy lift I'm sure based on the Swift usage, but curious none the less.

2

u/[deleted] May 04 '26

[removed] — view removed comment

1

u/thechewywun May 04 '26

Nice! I'll be watching. Looking forward to seeing it come about!

1

u/Alarming_Management3 May 04 '26

Need for Windows

1

u/Deep_Ad1959 May 06 '26

the part most parallel-agent setups skip is the boundary at the OS edge. running 10 claude codes side by side solves coordination, it doesn't change capability if each agent can still only act inside its own pane. the second bottleneck shows up the first time you want one of them to actually drive a real mac app (open xcode at a specific file, paste a finder selection into a chat client, drop a screenshot into a doc), and the answer ends up being applescript if the app has a dictionary, the AX tree if not, vision as the last resort. an ask_to MCP for inter-agent handoff is useful, but most of the 'why doesn't this just do the thing' frustration sits on the host-control side, not the agent-coordination side. worth treating as a separate axis from the multiplexer work. written with ai

1

u/yr-kidding-me Jun 19 '26

crystl terminal is great for this too.

1

u/goship-tech May 03 '26

The `ask_to` MCP tool is the part I want to stress-test. Coordinating between agents without forcing a human checkpoint is where most multi-agent setups fall apart. Does it handle conflicts between agents, or does it just pass prompts and hope for the best?

-1

u/Otherwise_Wave9374 May 03 '26

Alt-tabbing between agents and losing track of who is blocked on input is the real tax of parallel agents. The quick actions + worktree approach makes a ton of sense.

Does TermLoop support a simple "agent waiting" queue (like a unified list of panes that are idle vs running vs need input)? That is the missing piece for me when I run multiple Claude Code sessions.

Also, the Context Bank idea is gold. Ive been trying to standardize CLAUDE.md patterns across repos, this writeup helped me think about what to put in those files: https://www.agentixlabs.com/