ACP (Agent Client Protocol)

Run Maki inside your editor. maki acp starts an ACP server over stdio, so any ACP-capable editor (like Zed) can drive Maki as its coding agent.

maki acp

Zed setup

Add Maki as a custom agent in Zed's settings.json:

"agent_servers": {
  "Maki": {
    "default_config_options": {
      "model": "deepseek/deepseek-v4-flash"
    },
    "type": "custom",
    "command": "maki",
    "args": ["acp"],
    "env": {}
  }
}

The model value is a provider/model-id spec, same format as maki --model.

What works

• Sessions persist. Loading a session replays the full conversation in the editor, so you can resume where you left off.
• Model switching. Pick a model from the editor's dropdown, mid-session. All configured providers show up.
• Modes. Switch between build (full access) and plan (read-only) from the editor.
• Permissions. Tool permission prompts appear in the editor: allow or reject, once or always.
• Live tool calls. Tool progress streams as it happens, including sub-agents and batched calls.
• Images and context. Prompts can include images and editor-attached files.

Authentication, providers, and permissions come from your normal Maki config. Set up providers first and ACP sessions just work.