CLI Reference
The shipwright CLI is the main entry point for Shipwright. It routes to specialized scripts for each subcommand.
Setup & Diagnostics
shipwright init
One-command tmux setup with no prompts. Installs the tmux configuration, overlay, status widgets, and role-color hooks.
shipwright init # Standard installshipwright init --repair # Force clean reinstall (after OS upgrades)Flags:
| Flag | Description |
|---|---|
--repair | Force reinstall of all tmux config and plugins |
shipwright doctor
Validate your setup and diagnose common issues.
shipwright doctorChecks: tmux version, jq availability, overlay hooks, color configuration, orphaned sessions.
shipwright upgrade
Check for and apply updates.
shipwright upgrade # Check for updatesshipwright upgrade --apply # Pull latest and applyTeam Sessions
shipwright session
Create a team session with optional template.
shipwright session <name> # Bare sessionshipwright session <name> --template <template> # With templateshipwright session <name> -t feature-dev # Short flagFlags:
| Flag | Description |
|---|---|
--template, -t | Team template name (see shipwright templates list) |
shipwright status
Show the team dashboard with all active sessions.
shipwright statusAlso available via tmux keybinding: Ctrl-a then Ctrl-t.
shipwright ps
Show running agent processes across all sessions.
shipwright psshipwright logs
Tail agent logs for a session.
shipwright logs <session> # Show recent logsshipwright logs <session> --follow # Tail continuouslyContinuous Loop
shipwright loop
Run Claude Code autonomously until a goal is achieved.
shipwright loop "<goal>" [flags]Flags:
| Flag | Description | Default |
|---|---|---|
--test-cmd <cmd> | Test command for verification | auto-detected |
--audit | Self-reflection after each iteration | off |
--audit-agent | Dedicated auditor agent | off |
--quality-gates | Run tests as gates between iterations | off |
--definition-of-done <file> | Completion checklist | none |
--agents <n> | Number of agents | 1 |
--max-iterations <n> | Maximum iterations | 10 |
--model <model> | Claude model | default |
--resume | Resume interrupted loop | — |
Examples:
shipwright loop "Build user auth with JWT" --test-cmd "npm test"shipwright loop "Refactor API" --agents 3 --audit --quality-gatesshipwright loop "Build checkout" --definition-of-done requirements.mdshipwright loop --resumeSee Continuous Loop guide for details.
Delivery Pipeline
shipwright pipeline start
Start a new delivery pipeline.
shipwright pipeline start [flags]Flags:
| Flag | Description |
|---|---|
--goal <text> | Goal description |
--issue <number> | GitHub issue number |
--pipeline <template> | Pipeline template (standard, fast, full, hotfix, autonomous) |
--test-cmd <cmd> | Override auto-detected test command |
--agents <n> | Number of build agents |
--self-heal <n> | Max self-healing cycles |
--skip-gates | Auto-approve all gates |
--worktree | Run pipeline in a git worktree for isolation |
--worktree=<name> | Named worktree for parallel execution |
--slack-webhook <url> | Slack notification webhook |
shipwright pipeline resume
Resume a pipeline from where it left off.
shipwright pipeline resumeshipwright pipeline status
Show pipeline progress dashboard.
shipwright pipeline statusshipwright pipeline abort
Abort a running pipeline.
shipwright pipeline abortshipwright pipeline list
Browse available pipeline templates.
shipwright pipeline listshipwright pipeline show
View details of a pipeline template.
shipwright pipeline show <template>See Delivery Pipeline guide for details.
Daemon
shipwright daemon
Background daemon for autonomous issue processing with intelligent triage, adaptive templates, and self-optimizing metrics.
| Subcommand | Description |
|---|---|
shipwright daemon init | Initialize daemon configuration |
shipwright daemon start | Start background daemon |
shipwright daemon stop | Stop daemon |
shipwright daemon status | Show daemon status and active pipelines |
shipwright daemon metrics | DORA/DX metrics dashboard |
shipwright daemon logs | View daemon logs |
shipwright daemon triage | Show issue triage scores and priority |
shipwright daemon patrol | Run proactive codebase patrol |
Start flags:
| Flag | Description | Default |
|---|---|---|
--config <path> | Path to daemon-config.json | .claude/daemon-config.json |
--detach, -d | Run in a detached tmux session | off |
--no-github | Disable GitHub API calls (dry-run mode) | off |
Metrics flags:
| Flag | Description | Default |
|---|---|---|
--period <days> | Reporting period | 7 |
--json | JSON output | off |
Patrol flags:
| Flag | Description | Default |
|---|---|---|
--once | Run patrol once and exit | off |
--dry-run | Show findings without creating issues | off |
Examples:
shipwright daemon init # Generate config fileshipwright daemon start # Start watching in foregroundshipwright daemon start --detach # Start in background tmux sessionshipwright daemon start --config my-config.json # Custom configshipwright daemon status # Show active jobs and queueshipwright daemon stop # Graceful shutdownshipwright daemon logs --follow # Tail the daemon logshipwright daemon metrics # DORA + DX metrics (last 7 days)shipwright daemon metrics --period 30 # Last 30 daysshipwright daemon metrics --json # JSON output for dashboardsshipwright daemon triage # Show issue triage scoresshipwright daemon patrol # Run proactive codebase patrolshipwright daemon patrol --dry-run # Show what patrol would findSee Autonomous Daemon guide for details.
Fleet Operations
shipwright fleet
Multi-repo daemon orchestrator. Spawn daemons across repositories, view a fleet-wide dashboard, and aggregate DORA metrics.
| Subcommand | Description |
|---|---|
shipwright fleet init | Generate fleet-config.json (auto-detects sibling repos) |
shipwright fleet start | Start daemons for all configured repos |
shipwright fleet stop | Stop all fleet daemons |
shipwright fleet status | Show fleet dashboard (per-repo status) |
shipwright fleet metrics | Aggregate DORA metrics across repos |
Flags:
| Flag | Description | Default |
|---|---|---|
--config <path> | Path to fleet-config.json | .claude/fleet-config.json |
--period <days> | Reporting period for metrics | 7 |
--json | JSON output for metrics | off |
Examples:
shipwright fleet init # Generate configshipwright fleet start # Start all daemonsshipwright fleet start --config my-fleet.json # Custom configshipwright fleet status # Fleet dashboardshipwright fleet metrics --period 30 # 30-day aggregateshipwright fleet stop # Stop everythingSee Fleet Operations guide for details.
Bulk Fix
shipwright fix
Apply the same goal across multiple repositories in parallel. Each repo gets its own branch and pipeline run.
shipwright fix "<goal>" [flags]Flags:
| Flag | Description | Default |
|---|---|---|
--repos <dir1,dir2,...> | Comma-separated repo paths | — |
--repos-from <file> | Read repo paths from file (one per line) | — |
--pipeline <template> | Pipeline template | fast |
--model <model> | Claude model | auto |
--max-parallel <n> | Max concurrent pipelines | 3 |
--branch-prefix <prefix> | Branch name prefix | fix/ |
--dry-run | Show what would happen without executing | off |
--status | Show running fix sessions | — |
Examples:
shipwright fix "Update lodash to 4.17.21" --repos ~/api,~/web,~/mobileshipwright fix "Fix SQL injection in auth" --repos ~/api --pipeline fastshipwright fix "Bump Node to 22" --repos-from repos.txt --pipeline hotfixshipwright fix --statusSee Bulk Fix guide for details.
Memory
shipwright memory
Persistent learning and context system. Captures pipeline learnings, failure patterns, and design decisions per repository with cross-repo global memory.
| Subcommand | Description |
|---|---|
shipwright memory show | Display memory for current repo |
shipwright memory show --global | Display cross-repo learnings |
shipwright memory search <keyword> | Search memory for a keyword |
shipwright memory stats | Show memory size, age, and hit rate |
shipwright memory export | Export memory as JSON |
shipwright memory import <file> | Import memory from JSON |
shipwright memory forget --all | Clear memory for current repo |
Pipeline integration commands (called automatically by pipelines):
| Subcommand | Description |
|---|---|
shipwright memory capture <state> <artifacts> | Capture pipeline learnings |
shipwright memory inject <stage_id> | Inject context for a pipeline stage |
shipwright memory pattern <type> [data] | Record a codebase pattern |
shipwright memory metric <name> <value> | Update a performance baseline |
shipwright memory decision <type> <summary> | Record a design decision |
shipwright memory analyze-failure <log> <stage> | Analyze failure root cause via AI |
Examples:
shipwright memory show # View repo memoryshipwright memory show --global # View cross-repo learningsshipwright memory search "auth" # Find auth-related memoriesshipwright memory export > backup.json # Export memoryshipwright memory import backup.json # Import memoryshipwright memory capture .claude/pipeline-state.md .claude/pipeline-artifactsshipwright memory inject build # Get context for build stageSee Memory guide for details.
Cost Intelligence
shipwright cost
Token usage tracking, budget enforcement, and spending analysis.
| Subcommand | Description |
|---|---|
shipwright cost show | Show cost summary for current period |
shipwright cost budget set <amount> | Set daily budget (USD) |
shipwright cost budget show | Show current budget and usage |
shipwright cost remaining-budget | Return remaining daily budget (used by auto-scaler) |
Show flags:
| Flag | Description | Default |
|---|---|---|
--period <days> | Reporting period | 7 |
--json | JSON output | off |
--by-stage | Breakdown by pipeline stage | off |
--by-issue | Breakdown by issue | off |
Pipeline integration commands (called automatically by pipelines):
| Subcommand | Description |
|---|---|
shipwright cost record <in> <out> <model> <stage> [issue] | Record token usage |
shipwright cost calculate <in> <out> <model> | Calculate cost without recording |
shipwright cost check-budget [estimated_usd] | Check budget before starting |
Model pricing (USD per 1M tokens):
| Model | Input | Output |
|---|---|---|
| opus | $15.00 | $75.00 |
| sonnet | $3.00 | $15.00 |
| haiku | $0.25 | $1.25 |
Examples:
shipwright cost show # 7-day cost summaryshipwright cost show --period 30 --by-stage # 30-day breakdown by stageshipwright cost budget set 50.00 # Set $50/day limitshipwright cost budget show # Check current budgetshipwright cost calculate 50000 10000 opus # Estimate costSee Cost Intelligence guide for details.
Repo Preparation
shipwright prep
Analyze and prepare a repository for agent teams.
shipwright prep [flags]Flags:
| Flag | Description |
|---|---|
--dry-run | Preview without writing files |
--path <dir> | Target directory |
--force | Overwrite existing configs |
--no-hooks | Skip hook generation |
--no-claude-md | Skip CLAUDE.md generation |
--check | Check repo readiness without writing |
--update | Update existing configs (preserve edits) |
--with-claude | Run Claude analysis for smarter configs |
See Repo Preparation guide for details.
Maintenance
shipwright cleanup
Clean up orphaned tmux sessions and panes.
shipwright cleanup # Dry-run: show what would be cleanedshipwright cleanup --force # Actually clean upshipwright reaper
Clean up dead tmux panes (panes where Claude has exited).
shipwright reaper # One-shot cleanupshipwright reaper --watch # Background auto-cleanup every 5sshipwright reaper --dry-run # Preview what would be reapedAlso available via tmux keybinding: Ctrl-a then R.
shipwright worktree
Manage git worktrees for agent isolation.
shipwright worktree create <branch> # Create a worktreeshipwright worktree list # List worktreesshipwright worktree remove <branch> # Remove a worktreeshipwright templates
Browse team templates.
shipwright templates list # List all templatesshipwright templates show <name> # Show template detailsDashboard
shipwright dashboard
Real-time web dashboard for monitoring pipelines, agents, and daemon status.
shipwright dashboard # Start dashboard (foreground)shipwright dashboard start # Start in backgroundshipwright dashboard stop # Stop background dashboardRequires Bun runtime. The dashboard server runs on port 3000 and uses WebSockets for real-time updates.
Heartbeats
shipwright heartbeat
Agent liveness monitoring. Heartbeats are written automatically by pipeline agents and checked by the daemon for stale job detection.
| Subcommand | Description |
|---|---|
shipwright heartbeat list | Show all active heartbeats |
shipwright heartbeat check <job-id> | Check if a specific job is alive |
shipwright heartbeat clear | Remove stale heartbeats |
Heartbeat files are stored at ~/.shipwright/heartbeats/<job-id>.json.
Checkpoints
shipwright checkpoint
Save and restore pipeline state for resilience and recovery.
| Subcommand | Description |
|---|---|
shipwright checkpoint list | List saved checkpoints |
shipwright checkpoint save [name] | Save current pipeline state |
shipwright checkpoint restore <name> | Restore from a checkpoint |
Checkpoints are stored in .claude/pipeline-artifacts/checkpoints/.
Remote Machines
shipwright remote
Manage distributed worker machines for scaling pipeline execution across multiple hosts.
| Subcommand | Description |
|---|---|
shipwright remote list | Show registered machines |
shipwright remote add <name> --host <h> | Register a worker machine |
shipwright remote remove <name> | Unregister a machine |
shipwright remote status | Health check all machines |
Add flags:
| Flag | Description | Default |
|---|---|---|
--host <hostname> | Machine hostname or IP | required |
--path <path> | Shipwright install path on remote | required |
--user <user> | SSH user | current user |
--max-workers <n> | Max concurrent workers | 4 |
Machine registry is stored at ~/.shipwright/machines.json.
See Advanced Features for details.
Issue Tracking
shipwright tracker
Generic issue tracker integration that routes to provider-specific implementations.
shipwright tracker config # Show tracker configurationshipwright tracker notify <event> <issue> <data> # Send event to trackershipwright linear
Linear issue tracker integration for bidirectional sync between pipelines and Linear issues.
shipwright linear setup # Configure Linear integrationshipwright linear sync <issue> # Sync issue status to Linearshipwright jira
Jira issue tracker integration.
shipwright jira setup # Configure Jira integrationshipwright jira sync <issue> # Sync issue status to JiraConfiguration is stored at ~/.shipwright/tracker-config.json. See Issue Tracking guide for setup instructions.
Intelligence Layer
The intelligence layer provides AI-powered analysis and optimization. All intelligence features are behind feature flags and off by default — enable them in daemon-config.json.
shipwright intelligence
Core intelligence engine for semantic analysis, pipeline composition, cost prediction, and decision synthesis.
| Subcommand | Description |
|---|---|
shipwright intelligence analyze | Semantic analysis of issues for triage |
shipwright intelligence compose | AI-driven pipeline composition |
shipwright intelligence predict | Cost and complexity prediction |
shipwright intelligence synthesize | Synthesize findings into recommendations |
shipwright intelligence search-memory | Search cross-repo memory for patterns |
shipwright intelligence recommend-model | Recommend Claude model for stage |
shipwright intelligence cache-stats | Show intelligence cache statistics |
shipwright intelligence cache-clear | Clear intelligence cache |
Examples:
shipwright intelligence analyze '{"title":"Add auth","labels":["feature"]}'shipwright intelligence compose <issue_json>shipwright intelligence predict --stage build --goal "Refactor API"shipwright intelligence recommend-model --stage testshipwright optimize
Self-optimization and learning system. Analyzes outcomes, tunes template weights, and evolves routing decisions.
| Subcommand | Description |
|---|---|
shipwright optimize analyze-outcome | Analyze completed pipeline outcome |
shipwright optimize tune | Full outcome analysis and model tuning |
shipwright optimize report | Show optimization learnings and metrics |
shipwright optimize evolve-memory | Evolve memory from optimization data |
Examples:
shipwright optimize analyze-outcome .claude/pipeline-state.mdshipwright optimize tuneshipwright optimize report --period 30shipwright predict
Predictive analytics for risk assessment, anomaly detection, and proactive codebase patrol.
| Subcommand | Description |
|---|---|
shipwright predict risk | Pre-pipeline risk assessment |
shipwright predict anomaly | Compare metrics against running baselines |
shipwright predict patrol | AI-driven code analysis for high-risk code |
shipwright predict baseline | Update running metric baselines (EMA) |
Examples:
shipwright predict risk '{"title":"Add payment","complexity":7}'shipwright predict anomaly build duration 45.3shipwright predict patrol src/ --git-log commits.logshipwright developer-simulation
Multi-persona code review using simulated developer personas (security, performance, maintainability).
| Subcommand | Description |
|---|---|
shipwright developer-simulation review | Run 3-persona PR review |
shipwright developer-simulation address | Address reviewer objections |
Examples:
shipwright developer-simulation review <code_diff> "<PR description>"shipwright developer-simulation address <objections_json> "<implementation context>"shipwright adversarial
Red-team code review that finds security flaws, race conditions, and edge cases.
| Subcommand | Description |
|---|---|
shipwright adversarial review | Hostile security and QA review |
Examples:
shipwright adversarial review <code_diff> "<context>"shipwright architecture
Living architecture model: build, validate changes, and evolve patterns over time.
| Subcommand | Description |
|---|---|
shipwright architecture build | Build architecture model from codebase |
shipwright architecture validate | Validate code changes against model |
shipwright architecture evolve | Evolve model with intentional changes |
Examples:
shipwright architecture buildshipwright architecture validate <code_diff>shipwright architecture evolve architecture.json "Added event-driven patterns"Configuration:
All intelligence features are controlled via feature flags in .claude/daemon-config.json:
{ "intelligence": { "enabled": true, "analyze_enabled": true, "compose_enabled": true, "optimize_enabled": true, "predict_enabled": true, "adversarial_enabled": true, "simulation_enabled": true, "architecture_enabled": true }}See Intelligence guide for detailed setup and examples.