AIToday

One developer stops playing messenger between AI agents, wants them to talk directly

r/AI_Agents7h ago

Key takeaway

A developer describes the hidden cost of using multiple AI agents for code review and planning: even when copying context between them is easy, they end up spending more time reconciling conflicting feedback than they would with a single agent. The real solution, they argue, is letting agents discuss the work directly with each other instead of routing everything through a human middleman.

Summaries like this, in your inbox every morning.

Sign up free →

3 Key Points

  • What happened

    A developer realized that manually shuttling work between multiple AI models—pasting code plans from one agent to another for review, then arbitrating their conflicting suggestions—was turning them into a referee rather than saving time. They decided they wanted the agents to discuss the work directly instead of going through a human intermediary.

  • Why it matters

    When using multiple AI agents for tasks like code review or planning, the bottleneck is not moving context between them but the human overhead of collecting and reconciling their feedback. Direct agent-to-agent communication could eliminate that friction, making multi-agent workflows genuinely faster rather than just multiplying the number of prompts someone has to manage.

  • What to watch

    The developer's core insight is that agent-to-agent discussion—having one model challenge another's suggestions in real time—could replace the manual back-and-forth that currently demands human judgment. Whether this actually works depends on whether agents can productively debate trade-offs without needing human arbitration at every step.

Context & Analysis

The developer's experience exposes a counterintuitive inefficiency in multi-agent AI workflows: adding a second opinion does not automatically save time if a human must synthesize the results. The mechanical act of copying a plan or pointing both agents to the same files is trivial; the real cost emerges when agents disagree, because the human must then evaluate each suggestion on its merits, infer whether disagreement stems from missing context or genuine technical judgment, and predict how each agent would respond to the other's feedback. This creates a combinatorial complexity that grows with the number of agents and the length of their responses. The developer's proposed solution—enabling agents to challenge each other directly—suggests that the next generation of AI-assisted work may need to shift from a hub-and-spoke model (human at the center, agents as spokes) to a network model where agents can negotiate their own differences, at least within bounds set by the human user. Whether this is feasible depends on whether agents can reliably debate technical trade-offs without devolving into circular argumentation or requiring human intervention for every disagreement.

FAQ

What was the original workflow the developer was using?
They would build a plan with one model—for example, Claude Code—then paste the entire plan into another model (Codex) to get a second opinion. For code reviews, they would have one model review a diff, then submit the same diff to another model for a second read.
What was the main problem that made this approach inefficient?
When the second model returned suggestions, the developer had to go through every one, decide whether it was valid, figure out whether it was based on missing context, and determine whether the first model would agree or push back. This turned them into a messenger and referee between AI agents rather than saving time.

Discussion

No comments yet. Be the first to share your thoughts!

Log in to join the discussion

Related Articles

Stay ahead with AI news

Get curated AI news from 200+ sources delivered daily to your inbox. Free to use.

Get Started Free

Free · takes 30 seconds · unsubscribe anytime

1 minute a day. The AI essentials.

200+ sources · Email / LINE / Slack

Get it free →