Getting Started

Prerequisites

• Node.js 20+ — Multi-Claude uses ES modules and modern Node APIs
• Claude Code CLI — Workers are Claude Code sessions, so the CLI must be installed and authenticated
• A stable codebase — The repo floor should be stable (build/test passing, deps resolved)

Install

npm install -g @multi-claude/cli

Verify the installation:

multi-claude --version
multi-claude --help

Your First Run

1. Assess fitness

Before committing to a parallel run, check whether the work fits:

multi-claude plan evaluate \
  --work-class backend_law \
  --packets 6 \
  --coupling low

The fitness engine uses evidence from scored trials to recommend whether multi-claude is appropriate. A “strong fit” at 3+ packets for backend work means go. A “moderate fit” at 5+ packets for UI work means proceed with caution.

2. Create and freeze a blueprint

multi-claude blueprint init --template backend_law
multi-claude blueprint validate
multi-claude blueprint freeze

The blueprint defines the packet graph: which packets exist, their file ownership, dependency edges, wave structure, and verification gates. Once frozen (SHA-256 hashed), it’s immutable.

3. Start the run

multi-claude run

Workers claim packets and begin execution. Watch progress in real-time:

multi-claude console watch

4. Check next action

multi-claude console next

The next-action engine computes the highest-priority operator action from a 10-level priority cascade. It might tell you to approve a gate, resolve a hook, or just wait.

5. Generate handoff evidence

When the run completes:

multi-claude console outcome
multi-claude console handoff
multi-claude console export handoff --format markdown

This produces a review-ready brief with verdict, contributions, interventions, outstanding issues, and evidence references.

What’s Next

• Planning — Deep dive into fitness assessment and blueprint design
• Console Reference — All 18 console sub-commands explained