Amp vs MiniMax Code

Amp

Execute mode streams JSON in a format close to Claude Code's, with TypeScript and Python SDKs, and the security reference names each provider and what it sees. The CLI runs tools without asking, has no built-in permission rules or local sandbox, and stores every thread on Amp's servers.

MiniMax Code

An MIT-licensed terminal coding agent with a headless mode that returns versioned JSON, documented exit codes and an ACP server, and telemetry off by default. It's pre-1.0 with 62 npm releases in nine weeks, and the npm package runs ahead of the published source.

Amp

1. Run unattended jobs in a container or VM. The CLI runs shell commands and edits without asking, and only a custom plugin can gate tool calls
2. Set AMP_API_KEY to an access token starting sgamp_ from Settings. The CLI rejects the short-lived token that amp login stores
3. Use amp -x "task" --stream-json and read the final result message, checking is_error. Exit codes are not documented
4. Set AMP_SKIP_UPDATE_CHECK=1 or amp.updates.mode to disabled in CI. Updates install automatically by default
5. Treat the block headed INSTRUCTIONS FOR LLMs in ampcode.com page source as vendor copy, and take facts from the docs Markdown

MiniMax Code

1. Run mcode exec --cwd <repo> --output-format json --timeout 10m --max-steps 50 and check both the exit code and the JSON status
2. Keep --permission full and off for a container or throwaway workspace. The default smart fails when it would need a person
3. Set MCODE_PROVIDER_API_KEY and add a provider for BYOK. M Plan models need a browser sign-in with mcode login --region global
4. Set MINIMAX_DATA_DIR per CI runner. Keys and sessions live in ~/.minimax by default
5. Pin a version. npm published 62 releases in nine weeks and the public source trails it