cli-jaw MCP工具

2. Install CLI-JAW + all dependencies

curl -fsSL https://raw.githubusercontent.com/lidge-jun/cli-jaw/main/scripts/install-wsl.sh | bash source ~/.bashrc jaw dashboard bash "$(npm root -g)/cli-jaw/scripts/verify-fresh-install.sh"

From Windows PowerShell into WSL, run commands through a login shell so the WSL profile PATH is loaded:

</details>

<details>
<summary><b>Fresh-machine evidence</b> — maintainer release check</summary>

Run this on a clean VM before publishing installer changes. It writes environment snapshots, installer logs, the exact collector/installer/verifier scripts that ran, their SHA-256 hashes, verifier logs, and new-shell PATH probes into `~/cli-jaw-fresh-install-evidence-*`.

Your personal AI agent. 2 lines to install. 13 AI runtime surfaces in one dashboard.

English / 한국어 / 中文 / 日本語

</div>

Install

<details> <summary><b>Safe install</b> — for existing users who want minimal changes</summary>

```bash

macOS / Linux / WSL with Node.js 22+ already installed

npm install -g cli-jaw jaw dashboard ```

That's it. Open http://localhost:24576 for the manager dashboard. Per-instance agent Web UIs still run from http://localhost:3457 when you start jaw serve. Requires Node.js 22.4+.

First time? The default npm install initializes CLI-JAW and attempts native Claude setup. Other AI CLIs are optional; install them all during npm setup with CLI_JAW_INSTALL_CLI_TOOLS=1 npm install -g cli-jaw on macOS/Linux. On Windows, use the WSL install path below.

1. Install WSL (PowerShell as Admin)

wsl --install

Restart, open **Ubuntu**, then:

PABCD Orchestration (Plan → Audit → Build → Check → Done)

For complex tasks, CLI-JAW uses a structured 5-phase workflow. You approve every transition — nothing ships without your OK.

P (Plan) → A (Audit) → B (Build) → C (Check) → D (Done) → IDLE
   ⛔          ⛔          ⛔         auto        auto

State is database-persisted and survives restarts. Workers cannot modify files — only verify. Activate with jaw orchestrate, /orchestrate, or /pabcd; resume an active worklog explicitly with /continue. Forward phase transitions require evidence attestation, e.g. jaw orchestrate B --attest '{"from":"A","to":"B","did":"<what you did>"}' (C→D also needs pasted checkOutput and exitCode). Workflow helper slash commands include /plan, /interview, /deliberate, /planaudit, /review, /search, /goal, /goalplan, /team, /task, /fork, and /gd; /plan is a compatibility guide that explains "this is PABCD P" and points to the right next command instead of creating a second planning mode. /search <query> routes search intent through the active search skill: classify local vs external lookup, rewrite focused queries, discover candidate URLs, and only then use browser commands such as browser fetch for evidence verification. Bounded automation is expressed as /goal run ..., not a separate top-level /autopilot. Durable goals — /goal <objective> plus update/done/cancel/pause/resume — are functional and survive restarts, and a goal resume re-fires the work on every interface (Web/CLI included, not just messaging). AI-initiated goal pause --agent --audit arms a two-tap gate: one audit/finalizer continuation may run with pause_gate_pending, and if that turn exits with the gate still armed, goal_pause_gate_pending suppresses further auto-continuation until a productive checkpoint or a second audited pause. /gd is shorthand for /goal done --force (skips the completion evidence gate). /goal run (preflight/start/stop/status) is a tracking-only preview: it gates on preflight and tracks turn/dispatch budget, with enforcement still to come.

---

Optional JWC Runtime

JWC is optional and external-only. The default npm install and Electron desktop sidecar do not bundle jawcode, @jawcode-dev, @oven, bun, or a jwc payload. To use JWC, install the runtime into CLI-JAW's external prefix and opt in with the printed SDK path:

jaw jwc install
export JWC_SDK_PATH="/absolute/path/printed/by/jaw-jwc-install/sdk.js"
jaw jwc doctor

To remove the optional external JWC dependencies later:

jaw jwc clean

<details> <summary><b>macOS one-click</b> — don't have Node.js? This installs everything</summary>

curl -fsSL https://raw.githubusercontent.com/lidge-jun/cli-jaw/main/scripts/install.sh | bash
source "${ZDOTDIR:-$HOME}/.zshrc" 2>/dev/null || true
bash "$(npm root -g)/cli-jaw/scripts/verify-fresh-install.sh"

</details>

<details> <summary><b>Windows (WSL — Windows Subsystem for Linux)</b> — one-click from scratch</summary>

```powershell

Free options (no credit card needed)

copilot login # GitHub Copilot (free tier available) opencode # OpenCode — free models available kiro # AWS Kiro (free tier with AWS account)

→ syncs to Claude, Codex, Gemini, Kiro, OpenCode, Copilot, and Antigravity config files simultaneously

No more editing several different JSON files. Install once, every MCP-aware engine gets it. Grok CLI is a standard runtime here, but it is not counted as MCP-sync capable until Grok exposes a compatible config surface. Antigravity MCP sync is a separate config target from the `agy` runtime registry entry.

---

CLI Commands

```bash

Employees vs. Sub-agents

These are different things:

Use employees for "Frontend does CSS, Backend does API." Use sub-agents for "read these 5 files in parallel before deciding."

---

How It Compares

---

Troubleshooting

---