| 💾 Saved. d722711 k33g 6h ago | 1 | # How to use mini-me from an editor (ACP) |
| 2 | |
| 3 | This guide shows how to host `mm` inside an editor that speaks the Agent Client Protocol, such as Zed. It assumes `mm` is built and installed on your `PATH` (`./install.sh` copies it to `/usr/local/bin`), and that your model server is running. |
| 4 | |
| 5 | ## Steps |
| 6 | |
| 7 | 1. Register `mm` as an agent server in the editor, with the `-acp` flag. In Zed, add to `settings.json`: |
| 8 | |
| 9 | ```json |
| 10 | { |
| 11 | "agent_servers": { |
| 12 | "mini-me": { |
| 13 | "type": "custom", |
| 14 | "command": "mm", |
| 15 | "args": ["-acp"], |
| 16 | "env": { "AGENT_CONFIG": "/absolute/path/to/agent.yaml" } |
| 17 | } |
| 18 | } |
| 19 | } |
| 20 | ``` |
| 21 | |
| 22 | 2. Point `AGENT_CONFIG` at an absolute path. The editor launches `mm` with the project's directory as working directory, so a relative `./agent.yaml` would not be found. In ACP mode a relative `skillsDir` in that file is resolved next to the file, not next to the editor's working directory. |
| 23 | |
| 24 | 3. Open the agent panel and start a conversation. Each `bash`, `read_file`, `write_file` and `edit_file` call appears as a tool call; the editor asks you to allow it before it runs. `read_skill` runs without a dialog. |
| 25 | |
| 26 | 4. Read the logs when something looks wrong. In ACP mode nothing human-readable goes to stdout: the banner, the warnings and a `[acp] …` trail go to stderr, which Zed shows under `dev: open acp logs`. |
| 27 | |
| 28 | ## Variants |
| 29 | |
| 30 | - **Allow a tool for the whole session.** Pick "Allow bash for this session" in the permission dialog; the choice is remembered per tool until the session ends. |
| 31 | - **Cancel a running turn.** Use the editor's stop key (Escape in Zed). The agent answers the prompt with stop reason `cancelled` and keeps the commands that already ran in the history. There is no `/abort` over ACP. |
| 32 | - **Compress or restart the conversation.** Send `/compact` or `/new`; editors that list the agent's commands offer both in the slash-command menu. See the [slash commands reference](../reference/slash-commands.md#acp-mode). |
| 33 | - **Attach a file with `@`.** The editor's picker sends a `resource_link`, passed to the model as `[attached file: <path>]`; a path typed by hand as `@path` is understood the same way (see [`@path`](attach-a-file.md)). The model reads the file with its tools. |
| 34 | - **Run from a terminal to debug the protocol.** `mm -acp` reads JSON-RPC on stdin and writes it on stdout, one message per line. |
| 35 | |
| 36 | ## See also |
| 37 | |
| 38 | - The exact methods and capabilities exposed: [ACP reference](../reference/acp.md) |
| 39 | - Why the terminal and the editor share one loop: [architecture](../explanation/architecture.md) |