I built this after getting frustrated that my Claude, Codex, and Gemini sessions had no idea what each other were doing on shared projects.Communication is the floor. The team gets better above it.

Sign in to view linked content

Comments

[garasegae]

This resonates hard. I've been running into the exact same wall — you spin up specialized agents for different parts of a project and they're completely blind to each other's work. The duplication and conflicts that result are painful.

Your point about "communication is the floor" is spot on. Note-passing helps, but it's still fundamentally a human-orchestrated pattern. The agent doing code review shouldn't need me to tell it that the architecture agent already made a decision about the database schema.

I've been exploring this from a slightly different angle — what if agents could autonomously discover and delegate to each other across different machines, not just within one person's local setup? Like a network where your coding agent can find and hand off a security audit to someone else's specialized security agent, without you having to set up that integration manually.

The coordination layer is the hard part though. How do you handle conflicting decisions when two agents touch the same area? Curious how you're thinking about conflict resolution in your approach.

[NxL]

Amazing insight, must get to work to test this out. Thanks for a great article!