Skip to main content
Mux implements the Agent Client Protocol (ACP) to integrate with editors that support it. The mux acp command starts a stdio bridge that any ACP-compatible editor can spawn as a subprocess.
ACP is the “LSP for agents” and provides session management, tool delegation, and streaming. Mux uses ACP (not MCP) for its editor bridge.

​
Zed

Zed has native ACP support and does not require a plugin. Open Settings (Cmd+,) and add: 
{
  "agent_servers": {
    "Mux": {
      "type": "custom",
      "command": "mux",
      "args": ["acp"]
    }
  }
}

{
  "agent_servers": {
    "Mux": {
      "type": "custom",
      "command": "npx",
      "args": ["-y", "mux", "acp"]
    }
  }
}

​
Connect to a remote server

Pass --server-url and --auth-token in args: 
{
  "agent_servers": {
    "Mux": {
      "type": "custom",
      "command": "mux",
      "args": ["acp", "--server-url", "https://mux.example.com", "--auth-token", "<token>"]
    }
  }
}
Or set environment variables for any mux acp process: 
MUX_SERVER_URL=https://mux.example.com \
MUX_SERVER_AUTH_TOKEN=<token> \
mux acp

​
Neovim

Two plugins currently support ACP in Neovim. codecompanion.nvim added ACP support in v17.18. Add the adapter in your lazy.nvim config: 
require("codecompanion").setup({
  adapters = {
    mux = function()
      return require("codecompanion.adapters").extend("acp", {
        name = "mux",
        schema = {
          model = { default = "mux" },
        },
        args = { "mux", "acp" },
      })
    end,
  },
  strategies = {
    chat = { adapter = "mux" },
    inline = { adapter = "mux" },
  },
})
See the codecompanion ACP adapter docs for full options.

​
agentic.nvim

agentic.nvim is a dedicated ACP client. Requires Neovim 0.11 or newer. Add via lazy.nvim: 
{
  "carlos-algms/agentic.nvim",
  opts = {
    agents = {
      mux = {
        cmd = "mux",
        args = { "acp" },
      },
    },
  },
}

​
JetBrains

JetBrains ACP support requires the AI Assistant plugin (2025.3 or newer).
  1. Open the AI Chat tool window
  2. Click More (...) then Add Custom Agent
  3. Add the Mux entry to the acp.json that opens:
{
  "agent_servers": {
    "Mux": {
      "command": "mux",
      "args": ["acp"]
    }
  }
}
ACP is not supported in WSL-backed JetBrains projects.
See the JetBrains ACP docs for more information.

​
Flags and environment variables

FlagEnvironment variableDescription
--server-url <url>MUX_SERVER_URLURL of a running Mux server
--auth-token <token>MUX_SERVER_AUTH_TOKENBearer token for authenticated connections
--log-file <path>—Write ACP logs to a file (useful when your editor hides subprocess stderr)
MUX_AUTH_TOKEN is not read by mux acp. Use MUX_SERVER_AUTH_TOKEN.
If no --server-url is provided, mux acp first attempts to discover a running server via the lockfile in ~/.mux/, then starts an in-process server automatically when needed.

​
Troubleshooting

  • Logs hidden by your editor: use --log-file /tmp/mux-acp.log to capture ACP stderr output.
  • Connection refused: ensure Mux is running (mux server or the desktop app), or omit --server-url to let ACP auto-start in-process.
  • Tool calls are not delegated: the editor must advertise filesystem or terminal capabilities, and the workspace must use local runtime mode.