ACP integration - MiniMax Agent Docs

mcode acp runs MiniMax Code as an Agent Client Protocol server for editors and Agent hosts that support ACP.

ACP

Start the server

mcode acp

ACP communicates over stdin/stdout. stdout is reserved for protocol messages; logs and diagnostics go to stderr. Do not write natural language directly to the process or mix wrapper logs into stdout.

Editor configuration

An editor that supports custom Agent servers can use this pattern:

{
  "agent_servers": {
    "minimax-code": {
      "type": "custom",
      "command": "mcode",
      "args": ["acp"],
      "env": {}
    }
  }
}

If the editor cannot find mcode, set command to the absolute executable path and restart the editor to refresh PATH.

ACP capabilities and boundaries

The ACP host can receive:

Agent replies, reasoning, and tool status;
file locations and diffs;
permission prompts and questions;
cancellation;
model and Plan controls.

The exact UI and controls depend on the ACP client. Manage authentication with mcode login or mcode acp login --region <region>.

When should I use ACP?

Need	Recommended entry point
Show Agent replies, diffs, and permission prompts in an editor	ACP
Let the host handle questions, cancellation, and model controls	ACP
Complete one task in a terminal	`mcode` or `mcode exec`

​ACP

​Start the server

​Editor configuration

​ACP capabilities and boundaries

​When should I use ACP?

ACP

Start the server

Editor configuration

ACP capabilities and boundaries

When should I use ACP?