// install

Tell your agent: launch this.

If ChiefLab is missing, the agent attaches it itself and renders the launch room in the same chat turn. Drafts ready for your approval. No website visit, no setup cognition.

The agent runs this for you. Here it is if you'd rather run it yourself:

npx -y @chieflab/cli launch-here --intent "launch this"

One command. Detects repo + runtime, installs ChiefLab if missing, fires the launch call over HTTPS. Drafts render inline; nothing publishes until you approve.

Windows PowerShell: if npx is blocked by script policy, run npx.cmd -y @chieflab/cli launch-here --intent "launch this" instead.

// what that command does

  1. 01 Detects your repo + agent runtime (Cursor / Claude Code / Claude Desktop / Codex / Windsurf / Cline)
  2. 02 If ChiefLab isn't attached: mints a workspace + writes the MCP config + plants repo instructions
  3. 03 If already attached: skips install, reuses the existing workspace
  4. 04 Gathers repo context (package.json, README, git log, routes, pricing)
  5. 05 Fires the launch call over HTTPS — launch room renders in the same chat turn, drafts ready for approval

// if auto-detect misses

The CLI handles every supported runtime today. If you're inside an MCP host the CLI hasn't learned yet, or you want to wire ChiefLab by hand, manual setup paths exist:

// advanced — direct MCP, SDK, manual key, integrations
  • Direct MCP (HTTP + bearer) Skip the CLI; call the hosted endpoint from any HTTPS-capable runtime.
  • Quickstart docs Everything an agent or developer needs to call ChiefLab end-to-end.
  • For agents Agent-readable instructions. Trigger phrases, loop protocol, safety rules.
  • Mint a key manually When the CLI cannot run (rare). attach handles this automatically in the normal flow.