v0.1.0 · CLAUDE CODE PLUGIN · MIT

Split the task. Spawn the wave. Watch every pane.

A Claude Code plugin. One task becomes parallel agents, each in a visible wmux pane, each in a strict file zone. A reviewer checks consistency before you commit.

/plugin install wmux-orchestrator github

INTERACTIVE · WAVE-01

One task. Three agents. Parallel.

Press play. Three agents spawn. They finish. A second wave consumes their output. A reviewer closes the run. This is the plugin — minus the real Claude Code calls.

The simulator is a toy. The real plugin spawns actual Claude Code agents in wmux panes. See the repo.

MENTAL MODEL · ONE GLANCE

From one prompt to a parallel fleet.

The orchestrator splits your task into file-zoned subtasks, groups them into dependency-ordered waves, and spawns each subtask as its own Claude Code agent in its own visible terminal pane.

MECHANICS · END-TO-END

Six steps. Prompt to commit.

  1. STEP 01 · ANALYZE

    Read the codebase.

    Reads your codebase. Traces imports. Groups files into subtasks. No manual graph.

  2. STEP 02 · DECOMPOSE

    Cut clean file zones.

    Each subtask gets a strict allowed and excluded list. Tight coupling stays together. Shared types ship in the earliest wave.

  3. STEP 03 · WAVE 1

    Foundations, in parallel.

    Foundation agents run simultaneously in their own wmux panes. Types. Interfaces. Shared modules.

  4. STEP 04 · WAVE 2+

    Dependents consume results.

    Dependent agents spawn once the previous wave reports done. They receive prior results as context. Nothing is invented twice.

  5. STEP 05 · REVIEW

    Automated consistency pass.

    An automated reviewer checks types, imports, orphan exports. Minor issues auto-fix. The rest surface in the report.

  6. STEP 06 · SHIP

    Commit, diff, or abort.

    Three options. Commit the work. View the aggregated diff. Abort everything. No half-applied state.

ISOLATION · FILE ZONES

Strict zones. Zero collisions.

Every agent receives an allowed and excluded file list before it starts. Two agents cannot touch the same file. When an agent edits outside its zone, the tool call is rejected. No merge theatre. No lost work. No silent overwrites.

AGENT A · WAVE 01

src/auth/types.ts

shared types — foundation

AGENT B · WAVE 02

src/auth/service.ts

depends on types.ts

AGENT C · WAVE 02

src/auth/middleware.ts

depends on types.ts

ENVIRONMENTS · DIFF

The diff between with and without.

Same orchestration logic. Different execution surface. The delta is visibility and intervention.

 task decomposition               · same plan approval                    · same reviewer                         · same-agents run as invisible subagents+agents run in visible wmux panes-progress shown as a text spinner+progress shown as a live dashboard-no mid-run user intervention+type into any pane to intervene-wave transitions via Agent tool returns+wave transitions via SubagentStop hooks

QUICKSTART · 30 SECONDS

Install in 30 seconds.

Drop the plugin into Claude Code. Fire a task. Approve the plan. That's the loop.

claude-code · zsh
$ /plugin install wmux-orchestrator
Installed wmux-orchestrator v0.1.0
Hooks registered · SessionStart, PostToolUse, SubagentStop, Stop
$ /wmux:orchestrate "refactor auth to use JWT"
Analyzing codebase... traced 47 files across 3 modules.
Plan: 3 agents across 2 waves + reviewer.
Validate this plan? (yes / adjust / cancel)
$ yes

ARCHITECTURE

Three layers. No daemon. No magic.

Three moving parts. Each does one job. None of them poll. None of them run in the background.

LAYER 01 · SKILLS

The intelligence.

Codebase analysis. Task decomposition. Plan presentation. Review. The orchestrate skill drives the flow. The reviewer runs after every wave is done.

  • orchestrate/SKILL.md
  • reviewer/SKILL.md
  • wmux-detect/SKILL.md

LAYER 02 · HOOKS

The reactivity.

PostToolUse tracks per-agent activity. SubagentStop drives wave transitions. SessionStart handles crash recovery. Stop warns when an orchestration is still live.

  • PostToolUse
  • SubagentStop
  • Stop
  • SessionStart

LAYER 03 · SCRIPTS

The wmux operations.

Spawning agents in panes. Updating the dashboard. Writing state. Collecting results. Plain bash. Talks to the wmux CLI.

  • spawn-agents.sh
  • update-dashboard.sh
  • on-agent-stop.sh
  • collect-results.sh

Shared state is a JSON file in a temp directory. That's it.

ELSEWHERE

Source. Host. Marketplace.

GitHub amirlehmam/wmux-orchestrator wmux the host multiplexer Plugin marketplace amirlehmam/claude-plugins-official