ACP Quickstart

The @aicoach/acp CLI brings AI Coach into Zed natively — same toolbox as the MCP server, plus per-session model selection and editor-managed file ops via Zed's Agent Client Protocol.

Status: not shipped yet. ACP is intentionally outside MCP v1. While we collect usage data on the MCP server, install AI Coach as an MCP context server in Zed — see connect-zed-mcp for the same tools without the in-editor agent loop.

Planned install

npm i -g @aicoach/acp
aicoach-acp login   # device-code flow → key in OS keychain

Zed config

{
  "agent_servers": {
    "AI Coach": {
      "type": "custom",
      "command": "aicoach-acp",
      "args": []
    }
  }
}

"type": "custom" is required by Zed's agent_servers schema — without it the agent fails to launch with no clear error.

What's planned

Streamed completions from the AI Coach gateway, with per-session model picker (/model claude-opus-4-7).
Tool surface inherited from the MCP server (skills, marketplace, models, plus paid tools when they ship).
File reads/writes via ACP's client-side fs — Zed stays in control.
Paid tool calls trigger ACP request_permission ("Run T8 Backlink Checker for $0.40?").

Until then

Use the MCP quickstart to get the read-only tools live in Zed today.