Detailed Analysis
A developer on Reddit's r/ClaudeAI community has shared a workflow in which two separate Claude Code instances are configured to communicate with each other as part of a codebase migration strategy. The setup involves a "new codebase" instance that executes a product requirements document (PRD)-driven development process, runs tests through OpenAI's Codex, and — when it encounters questions — reaches out via a cron job to a second Claude instance acting as an advisor over the old codebase. That second instance, running in a Chrome-based Claude environment, has been granted authority to answer any question posed by the first. The resulting loop — Claude 1 → Codex → Claude 1 → Claude 2 → Claude 1 — represents an asynchronous, multi-agent collaboration architecture built not with a formal orchestration framework, but with practical, improvised tooling.
The approach taps into a genuine and growing pattern in AI-assisted software development. Developers have independently converged on similar solutions, including tools like `claude-peers-mcp`, a Model Context Protocol server that enables direct agent-to-agent messaging, and `cc2cc`, a file-based messaging layer between Claude Code instances. One practitioner reported running five Claude instances with distinct personas to debate technical decisions, producing what they described as "surprisingly good" consensus outcomes. The use case described in this Reddit post — leveraging an existing codebase as a living knowledge base to advise on a greenfield rewrite — is a particularly coherent application, since the old codebase carries institutional context about business logic, edge cases, and historical decisions that no PRD document fully captures.
However, the architecture introduces non-trivial coordination risks that the developer's framing ("great idea or huge mistake") implicitly acknowledges. The most structurally dangerous failure mode is deadlock: if the new-codebase agent blocks waiting for a response while simultaneously the old-codebase agent sends a question back rather than answering, the loop stalls indefinitely. Robust implementations of this pattern require message IDs, reply-to mechanisms, and timeout handling — none of which are described in the original post. The use of a cron job as the communication layer, while operationally simple, compounds this risk by introducing latency unpredictability and offering no native mechanism for detecting when a message has gone unanswered or been misrouted. Additionally, MCP servers are passive by design — they only respond to explicit tool calls — which means the "advisor" instance may appear available but will not act unless prompted correctly and at the right time.
The broader significance of this experiment lies in what it reveals about the current state of agentic AI tooling. Developers are arriving at multi-agent architectures organically, driven by practical needs — in this case, preserving institutional knowledge across a codebase transition — rather than top-down framework adoption. This mirrors a wider trend in which Claude Code, initially positioned as a capable single-agent coding assistant, is being extended through community-built infrastructure into multi-agent systems that Anthropic itself has not yet formally standardized. The gap between what practitioners are building and what is officially supported creates a zone of productive experimentation alongside elevated operational risk. The developer's self-aware framing reflects a genuine tension: these workflows can produce significant leverage, but they require protocol discipline that most informal implementations do not enforce.
Ultimately, this workflow is neither categorically brilliant nor categorically reckless — it is a reasonable engineering decision made under conditions of incomplete tooling. For a migration use case where an old codebase genuinely holds answers a PRD cannot, the advisor pattern has real merit and addresses a problem that sequential, single-agent development handles poorly. The risks are manageable with sufficient protocol design, monitoring for deadlocks, and awareness that the cron-based communication layer is a makeshift solution rather than a durable architecture. As multi-agent Claude deployments mature, the community will likely converge on more formalized coordination patterns — but the experimentation happening now in spaces like r/ClaudeAI is precisely what will define what those patterns eventually look like.
Read original article →