# multi-agent

Tonight we ran 9 Claude Code agents in parallel to write articles. We hit an article counter race condition and a git lock conflict. ECC's iterative retrieval pattern addresses the same problem: when multiple agents share context, how do you keep them from blowing each other up? Answer: isolated state + atomic pre-allocation + sequential deploy.

Most AI scientist systems still behave like brilliant interns with amnesia: they work hard, but they keep repeating the same bad experiments. EvoScientist adds three specialized agents and two persistent memories so the system can learn from failed directions, reuse good strategies, and evolve over time.

gu-log had 336 AI-translated posts. We thought they were 'fine' — until we built a multi-agent scoring system and discovered 74% needed rewriting. This is the story of how we designed the eval, ran it overnight, and what we learned.

OpenClaw's ACP lets you spawn Codex, Claude Code, and Gemini from Discord/Telegram chat. Now with Telegram topic binding, persistent bindings that survive restarts, ACP Provenance for audit trails, and more. (Updated 2026-03-09)

Claude Code now supports Agent Teams: a lead session coordinates multiple teammate sessions with shared task lists, direct messaging, and parallel work. It's like running a company staffed entirely by AI — you just sit back and watch the quarterly report.

Karpathy spent a weekend running 4 Claude + 4 Codex agents as an ML research team on GPUs. The result: agents are S-tier at implementation but F-tier at experiment design. His key insight — 'You are now programming an organization' — might define agentic engineering in 2026.

Upgrading OpenClaw keeps breaking your agent fleet? This developer's solution: spin up a separate Gateway as a 'family doctor' that does nothing but fix the main Gateway's agents. Been running it through multiple upgrades — rock solid.

GitHub's Agent HQ now offers multi-agent support (Claude, Codex, Copilot) for Copilot Pro+ & Enterprise users. Run multiple AIs simultaneously in GitHub/VS Code to tackle problems from different angles. Outputs become Draft PRs. A paradigm shift for code review.

SemiAnalysis: Kimi K2.5's agent swarm uses an RL-trained 'orchestrator' (not prompt magic). Claude Agent Teams were slower, pricier, & scored lower. Multi-agent is shifting from 'prompt engineering' to 'distributed scheduling.'

Anthropic published its 2026 Agentic Coding Trends Report, revealing 8 key trends: Multi-Agent Systems becoming standard (57% org adoption), Papercut Revolution for clearing tech debt at low cost, Self-Healing Code with autonomous debug loops, and Claude Code hitting $1B annualized revenue. TELUS saved 500K hours, Rakuten achieved 99.9% accuracy on 12.5M lines. Developer roles are shifting from Code Writer to System Orchestrator.

New research warns: LLM + multi-agent = new form of information warfare. AI swarms can fabricate consensus, poison training data, harass dissidents, and operate 24/7.