3 ms·
set up a channel for agents to communicate and you shouldn't have issues with messy merges. your force quitting is probably more from your build pipeline than
by otekengineering 2mo ago
set up a channel for agents to communicate and you shouldn't have issues with messy merges.
your force quitting is probably more from your build pipeline than anything agents are doing.
i use an m2 8gb air with no performance issues at up to 10 parallel claude code interactive sessions (ghostty), each with deep/transient subagent heirarchies that mix claude and codex.
very rarely need to force quit. only seen a couple restart-level failures, and those were on me for being cowboy with subagent delegation logic, resulting in 100s of claude moles popping up faster than i could whack them with force close.
- 4b11b4 2mo agoIn codex threads can inspect each other, rename themselves , send each other messages. communication is default primitive
- funador 2mo agoI do have a pretty heavy pipe line of local tests and running more than one of those at once is what spurred me to write this package. Especially the build step.