wolverin0

Theorchestra — Development skill for Claude Code

Development community

Agent-centric multi-agent orchestrator for Claude Code and Codex sessions, with WezTerm panes as the substrate.

How to install Theorchestra

This entry records only its repository, not the path inside it, so there is no exact command to give. Open wolverin0/theorchestra and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Theorchestra does

Agent-centric multi-agent orchestrator for Claude Code and Codex sessions, with WezTerm panes as the substrate.

Alternatives in Development

Alethe Agents — A local-first desktop workspace for running, organizing, and resuming multiple coding agents and shells with r 511 ★
Albert — Autonomous multi-agent harness for Claude Code (A.L.B.E.R.T. orchestrator) plus a zero-dependency live HUD con 100 ★
Jmux Control — Control jmux sessions, windows, and panes programmatically 83 ★

README

theorchestra

**Multi-agent orchestrator for Claude Code and Codex sessions, with WezTerm panes as the substrate.**

theorchestra lets you run many long-lived AI coding sessions in parallel — each in its own WezTerm pane — and gives them a shared protocol to talk to each other, intelligent session-reset when context fills up, domain-specialized personas, and a Telegram feed so you can read what they're doing from your phone.

The control surface is **Claude Code itself, acting as orchestrator** (the OmniClaude pattern) — using `mcp__wezbridge__*` tools to spawn, prompt, and read other panes. There is no separate browser UI; the daemon on :4200 exists only to back the MCP server.

     ┌──────────────────────────────────────────────────────────────────┐
     │                          WezTerm (mux)                           │
     │                                                                  │
     │  pane-6 OmniClaude    pane-2 coder       pane-3 reviewer         │
     │   (orchestrator) ──▶ (frontend lead)  ◀─▶ (plan-mode audit)      │
     │        ▲                  │                   │                  │
     │        │                  └── A2A envelope ───┘                  │
     │        │             via mcp__wezbridge__send_prompt             │
     │        │                                                         │
     │        │       dashboard-server.cjs @ :4200 (REST/SSE backend    │
     │        │       for the wezbridge MCP — no UI, daemon only)       │
     └────────┼─────────────────────────────────────────────────────────┘
              │
              ├─ omni-watcher ─────▶ stdout events (session state + A2A)
              ├─ tasks-watcher ────▶ active_tasks.md signals (stuck / follow-ups)
              ├─ auto-handoff ─────▶ readiness check → /handoff → /clear → resume
              └─ telegram-streamer ▶ live feed per pane → Telegram topic