> whenever one needs something from the other, they message each other via that file. Tasks can bounce back and forth as issues are resolved and tested.
replyWhy isn't this just one coherent agent loop with subtools/agents as appropriate? If these tasks are related in some way, having a single context would probably make it go much better.
The freewheeling messaging part is where the token bloat is coming from. I suspect that for some of us this is actually the point. I think it's a mostly form of entertainment to do things this way. The next logical step from Factorio gameplay.
Parallel agents remind me a lot about multi core compute. It's incredibly easy to take a single core product and make it run much worse across a lot of cores.
Yeah I keep getting “bell curve meme” vibes when I read about all these super complicated handrolled ways people have of getting multi agent setups to work… I’m more likely to be at the caveman end of the spectrum than the guru end but things are moving so fast, by the time I’ve heard about or vaguely understood these esoteric techniques I can usually trust that if they are any good then the good folks at Anthropic et al have already built it into the default behaviour of the harness. Reminds me of the obsession people have with wrapping a repository pattern around Entity Framework because it proves how clever they are.
replyWhy not use the native inter-session messaging in Claude Code?
reply[flagged]
reply