Back to corpus
research notebacklog referencescore 26

Three AIs, One Terminal: How I Built Cross-Model Live Collaboration

I asked Claude Code about the pane orchestrator. Then I asked OpenAI Codex the same question, without giving it any context about pane awareness. Codex gave me a detailed technical breakdown: the 5-phase heartbeat cycle, the KL divergence invariants, the security patches from last week, the bridge file schema. Everything.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

I asked Claude Code about the pane orchestrator. Then I asked OpenAI Codex the same question, without giving it any context about pane awareness. Codex gave me a detailed technical breakdown: the 5-phase heartbeat cycle, the KL divergence invariants, the security patches from last week, the bridge file schema. Everything. That moment made me stop and actually think about what I had built. Not a task dispatcher. Not a multi-model API wrapper. Something closer to a shared nervous system for three competing AI agents running simultaneously on the same machine. - **Claude Code** (Anthropic, Opus 4.6) across multiple panes, hooks into the OS - **OpenAI Codex CLI** (GPT-5.4) on `/dev/ttys001` in `--dangerously-full-access` mode - **Gemini CLI** (Google, Gemini 3 Pro) on `/dev/ttys009` in `--yolo` mode Each runs in its own terminal pane. Each has its own context window, its own company's model, its own personality. But they all read from the same underlying infrastructure: the same pane registry, the same task ledger, the same event bus, the same memory files. Codex has a bootstrap digest. It's a 37KB TypeScript script called `bootstrap-digest.ts` that runs at session start and reads everything:

Promotion decision

What has to happen next

Keep in the searchable backlog until it intersects a live paper or system.

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.