By WingsOfPanda
Multi-model tmux pane orchestration for Claude Code — spawn codex/agy/claude TUIs as attachable clone troopers
Run a cross-verified multi-model investigation on `$ARGUMENTS`. Master
> **Do not invoke directly.** This file is referenced by
Advisor-driven autoresearch — conductor plans, 2-3 codex troopers execute experiments persistently, advisor decides metric/dispatch/stop adaptively
Run a trooper-implements / Yoda-verifies pipeline on `$ARGUMENTS`.
Show active troopers (panes + state); optionally scoped to a topic
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Spawn Codex, Gemini, and Claude as real tmux panes you can attach to mid-task.
Clone Wars is a Claude Code plugin that turns multi-model orchestration into something
you can watch live. Every model becomes a clone trooper — a named tmux pane
(captain rex (codex), commander cody (claude), commander wolffe (opencode)) running
its native TUI, talking to your Claude Code session via inbox/outbox files. Panes survive
Master Yoda crashes; you can tmux select-pane mid-task and see exactly what each model
is doing.
Install · Quickstart · Commands · Design
When Claude Code dispatches a Claude teammate, you see it work in a real pane. When that teammate shells out to Codex or Gemini, you don't — the model runs as a hidden subprocess. You lose visibility, you lose mid-task intervention, you lose the conversation.
Clone Wars closes that gap. Every model gets a real attachable pane with the same
observability as a Claude teammate. File-based IPC replaces in-process SendMessage, so
panes survive crashes and stay forensically reconstructable after teardown.
/plugin marketplace add WingsOfPanda/clone-wars
/plugin install clone-wars@clone-wars
Then, inside a tmux session:
/clone-wars:medic
Medic verifies tmux ≥ 3.0, your $CLONE_WARS_HOME, the shipped configs, and per-provider
binary availability. Missing providers WARN (you don't need all three); zero healthy
providers FAIL.
/clone-wars:spawn rex codex auth-review "review src/auth/oauth.py for token-refresh edge cases"
/clone-wars:list
/clone-wars:collect rex auth-review
/clone-wars:teardown auth-review
What just happened:
captain rex (codex) in Rex's blue, started Codex
inside it, injected the trooper identity prompt, and dispatched the review task.{event: "done"} in his outbox, then prints the summary.$CLONE_WARS_HOME/archive/... for forensics.Each trooper is identified by <commander>-<model>-<topic>: a name from a curated pool
(rex, cody, wolffe, fives, echo, ...), the model it runs (codex / agy /
claude / opencode), and the operation slug. Multiple troopers can run on one topic; multiple topics
run concurrently.
| Command | What it does |
|---|---|
/clone-wars:medic | Health-check: tmux + $CLONE_WARS_HOME + configs + provider binaries. Run before spawning. |
/clone-wars:spawn <commander> <model> <topic> [--mode full|read-only] [prompt] | Open a tmux pane running the model's TUI. commander is a name from the pool, or random. --mode read-only sandboxes the trooper. Optional prompt is dispatched as the first task. |
/clone-wars:send <commander> <topic> <msg-or-@file> | Write a task to a trooper's inbox; the pane reads it on nudge. @path inlines a file. |
/clone-wars:collect <commander> <topic> [--timeout s] | Block until the trooper reports done or error, then print the summary. Exits non-zero on error/timeout so Master Yoda can chain commands. |
/clone-wars:list [<topic>] | Show active troopers across topics, or scope to one. Flags [ORPHAN] panes for cleanup. |
/clone-wars:teardown <topic> / <commander> <topic> / --all | Graceful shutdown: 8s colored banner, then kill the pane and archive state. |
/clone-wars:deploy [<design-path>] | Codex implements + Yoda verifies a design doc. |
/clone-wars:meditate <topic> | Deep multi-aspect exploration: parallel-N research, preliminary synthesis, 5-signal confidence gate, adversary phase, tradeoff-matrix landscape doc with directional Conclusion that feeds /clone-wars:consult. |
/clone-wars:deep-research <topic-with-metric> | Advisor-driven executable autoresearch. 2-3 long-lived codex troopers (PhD-student model) spawned once; advisor (Yoda) discusses the metric with the user, then dispatches experiments adaptively across the session. Stops on time-budget hit or 5-experiment stagnation. ⚠️ runs codex with sandbox bypass — read DANGER block below. |
/clone-wars:deep-research/clone-wars:deep-research spawns codex troopers under
--dangerously-bypass-approvals-and-sandbox and has them write +
execute arbitrary code in your repo. v1 sandboxing is honor-system
— troopers are told to stay inside their per-branch sandbox dir, but
enforcement is not mechanical.
Net access is permitted by default in v0.27.0 (was opt-in via
--allow-net in v0.26.0; the flag was removed). Troopers may install
dependencies and download datasets as needed.
npx claudepluginhub wingsofpanda/clone-wars --plugin clone-warsMulti-model tmux pane orchestration for Claude Code — spawn codex/claude/agy/opencode TUIs as attachable parts
Memory compression system for Claude Code - persist context across sessions
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Unified status line for Claude Code with multi-CLI (Claude, Codex, Gemini, z.ai) usage monitoring, context, rate limits, and cost tracking
Editorial "Web Designer" bundle for Claude Code from Antigravity Awesome Skills.