Back to corpus
architecturetechnical paper candidatescore 54

CALC: Cross-Agent Live Collaboration

CALC connects three AI coding agents from three different companies into a unified collaboration system. The agents share context, route tasks by model strength, and communicate through five transport layers.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

# CALC: Cross-Agent Live Collaboration ## Architecture Document v1.0 > Date: 2026-03-09 | Author: Mohamed Diomande | Status: Production CALC connects three AI coding agents from three different companies into a unified collaboration system. The agents share context, route tasks by model strength, and communicate through five transport layers. The problem it solves is simple: when multiple AI agents run on the same machine, they're blind to each other. Each one starts fresh, unaware of what others have done, are doing, or need. The old approach (the Cortex Orchestrator auto-injector) solved half of this by detecting idle panes and pasting tasks into them. But it was unidirectional, one-shot, and model-agnostic. CALC replaces that with bidirectional, persistent, model-aware collaboration. The discovery that triggered CALC: Codex answered a question about the pane orchestrator without being told anything about it. It synthesized the answer from shared state files that its bootstrap digest reads at session start. Gemini, lacking a bootstrap digest, could not answer the same question. The gap between "connected" and "disconnected" was visible in a single prompt. | Property | Value | |----------|-------| | Model | Opus 4.6 (claude-opus-4-6) | | Provider | Anthropic | | TTY | Multiple (s003 through s012, varies by session) | | Mode | `--dangerously-skip-permissions` | | Context Window | 200K tokens | | Integration | Native hooks (17 events), 15 MCP servers, NUMU (implicit), mesh bus (via hooks) |

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.