Using Mirri Code in IDEs

Mirri Code supports integration into IDEs via the Agent Client Protocol (ACP), letting you use AI-assisted coding directly inside your editor.

Prerequisites

Before configuring your IDE, make sure Mirri Code is installed and a model provider is configured (add one in the web UI's settings, or edit ~/.mirri-code/config.toml directly).

The ACP adapter is exposed as the mirri acp subcommand. The IDE launches it as a child process and communicates over stdin/stdout using JSON-RPC. Sessions reuse your existing provider configuration from ~/.mirri-code/config.toml.

Path note

Child processes launched from an IDE GUI on macOS typically do not inherit the terminal shell's PATH. If mirri is not in a system directory like /usr/local/bin, use the absolute path in your IDE configuration. Run which mirri in a terminal to find the active path.

Using Mirri Code in Zed

Zed is a modern editor with native ACP support.

Add the following to Zed's config file at ~/.config/zed/settings.json:

{
  "agent_servers": {
    "Mirri Code": {
      "type": "custom",
      "command": "mirri",
      "args": ["acp"],
      "env": {}
    }
  }
}

Configuration fields:

• type: fixed value "custom"
• command: path to the Mirri Code executable. If mirri is not on PATH, use the full path (e.g. /Users/you/.local/bin/mirri).
• args: startup arguments. The acp subcommand switches the CLI into ACP mode.
• env: additional environment variables; usually leave this empty. Zed injects a default environment automatically.

After saving, open a new conversation in Zed's Agent panel and it will launch a Mirri Code ACP subprocess using the configuration above. MCP servers declared in Zed's agent_servers section are also forwarded to the mirri side via the ACP protocol.

Using Mirri Code in JetBrains IDEs

JetBrains IDEs (IntelliJ IDEA, PyCharm, WebStorm, etc.) support ACP through the AI chat plugin.

If you do not have a JetBrains AI subscription, you can enable llm.enable.mock.response in the Registry to access the AI chat panel in ACP-only scenarios. Press Shift twice and search for "Registry" to open it.

In the AI chat panel menu, click Configure ACP agents and add the following configuration:

{
  "agent_servers": {
    "Mirri Code": {
      "command": "~/.local/bin/mirri",
      "args": ["acp"],
      "env": {}
    }
  }
}

JetBrains is strict about the command field — always use an absolute path, which you can get by running which mirri in a terminal. After saving, Mirri Code will appear in the AI chat's agent selector.

Using Mirri Code in Paseo

Paseo is a self-hosted orchestrator that runs and supervises agent CLIs from your desktop, web, and mobile. It connects to Mirri Code over ACP, the same way an IDE does.

Pick Mirri Code from Paseo's built-in ACP provider catalog, or add a custom provider in ~/.paseo/config.json:

{
  "agents": {
    "providers": {
      "mirri": {
        "extends": "acp",
        "label": "Mirri Code",
        "command": ["mirri", "acp"]
      }
    }
  }
}

Paseo's generic ACP adapter does not drive provider configuration, so configure a provider and model in the CLI first (see Prerequisites) if you haven't already.

Troubleshooting

• Session disconnects immediately / IDE shows "agent exited": usually a wrong command path or a missing provider configuration. Run mirri acp in a terminal first to verify — if it blocks waiting for stdin, the CLI itself is fine and the problem is in the IDE configuration; if it exits immediately with an error, follow the error message (most commonly the provider and model need to be configured first).
• IDE shows "auth required": the CLI has no usable provider credentials. Exit the IDE, configure a provider and model in the web UI's settings (or edit ~/.mirri-code/config.toml), then restart the IDE.
• MCP tools not visible: check the mirri acp reference capability table to confirm that the MCP transport type configured in your IDE is supported. The Mirri Code ACP adapter currently supports http, stdio, and sse transports; acp transport MCP servers are silently dropped and a warning is written to the log.

Next steps

• mirri acp reference — ACP capability matrix and method coverage details
• mirri command reference — full subcommand list