Track MiniMax Code agent entry for the ACP Registry

[hetaoBackend]

Agent

MiniMax Code (mcode) is planned for public npm distribution as @minimax-ai/code. Its ACP server command is mcode acp.

The Registry entry is the intended discovery path for clients such as Zed and DeepChat; no client-specific extension or built-in registration should be needed.

Contribution plan

I plan to submit the Registry entry from hetaoBackend. A schema-valid draft is already prepared on the fork branch:

https://github.com/hetaoBackend/registry/tree/feat/minimax-code-agent

The entry uses a pinned npm version and args: ["acp"], together with the required 16x16 monochrome SVG icon.

Current gates

• The public @minimax-ai/code release is intentionally scheduled for 2026-08-16. The package is not expected to resolve from the public npm registry before that date.
• Final URL validation and the auth probe must run against the actually published artifact; no upstream entry PR should be opened before that succeeds.
• Terminal-auth validator compatibility is tracked separately in Align terminal-auth validation and docs with the current ACP RFD #498.

Once the public package and auth probe are green, I will refresh the pinned version if needed, run the full Registry verification, and open the entry PR.