# Fix list: MiniMax Code From Anchor Terminal's listing at https://www.anchorterminal.com/tools/minimax-code, the October 2026 research run, assessed 19 October 2026. Grade B, 67.5 out of 100. This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public. For a coding agent working on MiniMax Code: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published. ## 1. Security & auth, 57 out of 100, up to 7.5 more on the total Why it scored 57: Harness reading of the framework checklist. 30 for credentials and what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. Provider keys are read from an environment variable and never printed, and stored in `config.yaml` in the data directory. All three telemetry channels are off by default and the doc lists every field sent. The default `smart` policy classifies actions through a cloud classifier, and what it sends isn't documented (20). Ask, Auto and Full access in the TUI. Headless defaults to `smart` and fails on a pending permission request instead of approving it, while `full` and `off` skip checks. A bundled sandbox runtime with macOS tests, a read-only filesystem policy for Explore subagents when sandboxing is available, but the default sandbox coverage isn't documented (12). SECURITY.md says permissions and sandboxing don't replace review of untrusted plugins, MCP servers and shell commands. No guidance found for fetched web content (6). Sessions kept locally, `/export` with credential redaction, `/transcript` and stream-json events (11). SECURITY.md takes private reports by email and GitHub's private advisories with no response SLA, history and build scans with Gitleaks are recorded, and OSV lists no advisories. No security.txt (8). Total 57. The checklist (https://www.anchorterminal.com/benchmark/#checklist-security): - 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option. - 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions. - 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10. - 0 to 15, audit logs or per-call visibility for the operator. - 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public. Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing. ## 2. Reliability, 63 out of 100, up to 7.4 more on the total Why it scored 63: Local-package reading, for the CLI. An install script for macOS, Linux and WSL and one for Windows, and npm `@minimax-ai/code` with Node.js 22.19+, 24.2+, 25 or 26 stated. The installer doesn't support Alpine or musl (20). A public 'Source verification' workflow builds and tests on push and pull request, and shields.io reported its checks passing on main on 19 October. The repository's own verification record marks fresh cross-platform acceptance as not run, and the npm releases aren't shown to come from this source (20). 91 issues open against 229 closed and 11 pull requests open against 166 closed, read through shields.io. The repository also takes desktop-app issues, and which open issues are crashes or regressions couldn't be read, so the line scores the counts alone (15). A dated CLI changelog with Added, Improved and Fixed headings, but no breaking-change label, and its latest entry (0.6.7, 10 October) trails npm's 0.6.12 (8). 0.6.x and called a source preview (0). Total 63. The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability): Hosted APIs, MCP servers, models and platforms. - 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own). - 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so. - 15, rate limits documented with numbers. - 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved. - 10, an SLA published for any paid tier. - 10, the surface agents use is generally available, not beta or preview. Local packages, SDKs, frameworks and stdio MCP servers. - 20, installs from an official package with supported runtimes stated. - 25, a public CI and test suite, passing on the default branch. - 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered). - 15, semver discipline and breaking changes called out in a changelog. - 15, version 1.0 or later, or declared stable. Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors. ## 3. Payments & pricing, 60 out of 100, up to 5 more on the total Why it scored 60: Self-hosted rule. No payment protocol (0). The CLI is free under MIT with nothing to buy (20). No card or MiniMax account is needed for the software, and BYOK works without a login (20). An agent can install it from npm and run `mcode exec` with a provider key and no sign-up (20). M Plan and MiniMax API usage are separate purchases. Total 60. The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments): The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/). - 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which. - 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login. - 20, a free tier or trial that doesn't need a card. - 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API). Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied. Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol. ## 4. Agent ergonomics, 75 out of 100, up to 4.1 more on the total Why it scored 75: Harness reading, for a pipeline driving the CLI. Lightweight mode sends no tool schemas, Plan mode is separate from permissions, and `/btw` side chats run without blocking the main task. No per-tool allow or deny list was found in the CLI docs (14). json and stream-json output, `--timeout`, `--max-steps`, `--output-schema` and `--output-last-message` (18). Exit codes per failure class, a status field and an interaction error when a run would need a person (17). `--session`, `--continue`, fork and rewind, and a model request is retried when the first response doesn't arrive within 300 seconds (16). One positional argument runs a task and BYOK needs no MiniMax login, but there's no SDK package (10). Total 75. The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics): - 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries). - 20, pagination, filtering and output-size controls. - 20, actionable, documented error responses, codes and messages an agent can recover from. - 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations. - 15, sensible defaults, few required parameters, and official SDKs in at least two languages. Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs. ## 5. Transparency & trust, 61 out of 100, up to 3.4 more on the total Made of editorial 56, provenance 65. Why it scored 61: First-party code is MIT, with the bundled sandbox runtime under Apache-2.0 and the desktop app closed. The repository says the published npm package isn't shown to be built from this source, and npm is at 0.6.12 while the source is at 0.6.5 (22 of 30). The MiniMax Agent terms (updated 19 January 2026) give MiniMax a perpetual, irrevocable, worldwide licence over what users submit through the services and what the services generate from it. The privacy policy of the same date states no retention period and says nothing on training, and the telemetry doc says server-side retention isn't defined. BYOK runs that don't touch MiniMax's services aren't covered by either (8 of 30). No deprecation policy. Removed functions are listed in the changelog without dates ahead (6 of 20). Telemetry is off by default, with each field, each destination and two environment opt-outs documented (20). Total 56. The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency): - 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms. - 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors). - 0 to 20, a deprecation policy or notices with dates. - 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted). The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two. Provenance checks not met in full (half of this category, computed from checked facts): - Domain age: minimax.io, registered 2021-03-27 (5 years) (11 of 15) - Terms of service: read, states 6 of the 7 things a reader expects, and has 2 clauses that cost points (5.1 of 10) - Privacy policy: read, states 7 of the 8 things a reader expects (9.3 of 10) - Status page: not found (0 of 10) - security.txt: not found (0 of 10) ## 6. Schema & documentation, 81 out of 100, up to 3.1 more on the total Why it scored 81: Harness reading. `mcode exec` returns a versioned `ExecResult` JSON document (`schemaVersion` 1) or versioned stream-json events, takes `--output-schema` for the final answer, and `mcode acp` speaks the Agent Client Protocol. No OpenAPI, since there's no server API (20). llms.txt indexes the docs, and each page is served as Markdown (10). The security page says when to use each permission policy and to keep `full` and `off` to isolated workspaces, and the automation page gives a CI baseline (16). An options table with defaults and enums for permission, output and prompt modes (12). Examples for each mode, a nine-row exit-code table, five result statuses and a named error for invalid structured output (13). A dated CLI changelog in the docs, five npm releases behind (10). Total 81. The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema): APIs and MCP servers. - 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool). - 10, llms.txt or Markdown docs served for agents. - 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference. - 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs. - 0 to 15, examples and documented error responses. - 15, versioning and a public changelog. Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference. ## 7. Maintenance & community, 77 out of 100, up to 2 more on the total Why it scored 77: 0.6.12 on npm on 15 October 2026 (30). 62 npm releases from 0.1.0 on 14 August to 0.6.12 on 15 October, all in the last 90 days (20). 229 issues and 166 pull requests closed against 91 and 11 open, and 137 commits in the last month, but pull requests are taken only from collaborators and reply times couldn't be read (14). No SDK package. ACP ships inside the CLI (5). CI pins its GitHub Actions by commit, and the root package pins overrides for vulnerable dependencies (8). Total 77. The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance): - 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older. - 20, at least three releases or dated changelog entries in the last 90 days. - 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15. - 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models). - 10, package health, current dependencies and CI. Models are read for deprecation notice periods and model churn rather than release counts. ## What we couldn't check What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it. - What the `smart` and Auto permission policies send to MiniMax's cloud classifier - Which tool actions run inside the sandbox by default, outside Explore subagents - Whether the npm releases after 0.6.5 match any published source - unchecked: reply times on issues, and which of the 91 open issues concern the CLI rather than the desktop app. GitHub's pages weren't read, counts came from shields.io - Server-side retention for telemetry and diagnostics, which the repository says it doesn't define ## Weaknesses - Pre-1.0 and labelled a source preview, with npm at 0.6.12 and the public source at 0.6.5 - The default headless policy sends actions to a cloud classifier, and what it sends isn't documented - Which actions run inside the sandbox by default isn't documented - The CLI changelog trails npm by five releases - The MiniMax Agent terms take a perpetual, irrevocable licence over what users submit through MiniMax's services and what they generate, and the privacy policy states no retention period ## What costs an agent a turn today The notes we give agents before they call it. Each one is a workaround an agent shouldn't need. - Run `mcode exec --cwd --output-format json --timeout 10m --max-steps 50` and check both the exit code and the JSON `status` - Keep `--permission full` and `off` for a container or throwaway workspace. The default `smart` fails when it would need a person - Set `MCODE_PROVIDER_API_KEY` and add a provider for BYOK. M Plan models need a browser sign-in with `mcode login --region global` - Set `MINIMAX_DATA_DIR` per CI runner. Keys and sessions live in `~/.minimax` by default - Pin a version. npm published 62 releases in nine weeks and the public source trails it ## What the review panel asked for - breaking-change labels in changelog - dated deprecation notices - Keep the changelog current with releases - Document the classifier request - Document 429 and retry behaviour - Publish a status page - document classifier payload - publish source per release ## When it's done Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.