Engineers are the bottleneck: the case for cross-engineer agent-to-agent communication
thomasahle · x · 2026-11-09
Engineer thomasahle raises a practical workflow question: as engineers manage larger teams of agents, humans become the communication bottleneck. He proposes enabling cross-engineer agent-to-agent communication:
- Agents could negotiate API changes to prevent conflicting work
- Request UI changes from each other, notify about failing tests
- Provide expert guidance on how to use a system
He leaves open the design question: is GitHub enough? Should agents chat on Slack or an internal message board? Or should a company just run one big swarm that all engineers talk to?
More from coding & agent
- Day 309/365 of GPU Programming: Optimizing LLaMA2-7B on Edge with SIMD and Multithreading — NandoDF · 2026-11-09
- Berkeley-led paper: evolved agents gain 5.2 reliability points while losing 10 tasks they once solved — rohanpaul_ai · 2026-11-09
- Running a Home Mac mini as an Always-On Node for Remote AI Tasks — xiaohu · 2026-11-09
- Capwise repo goes public: native macOS screen recording and AI editing workbench — vista8 · 2026-11-09
- Capwise open-sources beta of AI screen recorder with bilingual captions and Agent CLI — vista8 · 2026-11-09
- Agent PRs merge at just 32.7% vs 84.4% for humans, with 91% more review time — gerardsans · 2026-11-09