# MiniMax Code vs Paseo (slim)

> MiniMax Code scores 66.1 (B) to Paseo's 62.1 (B) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/minimax-code-vs-paseo.md (~5,050 tokens) · this version ~1,480 tokens · JSON https://www.anchorterminal.com/compare/minimax-code-vs-paseo.json · canonical https://www.anchorterminal.com/compare/minimax-code-vs-paseo
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

MiniMax Code scores 66.1 (B) on agent readiness against Paseo's 62.1 (B), and leads in 4 of 7 scored categories. Paseo leads on transparency & trust. Both do agent harnesses.

- MiniMax Code: B 66.1, rank #382 of 1486 · https://www.anchorterminal.com/tools/minimax-code.min.md
- Paseo: B 62.1, rank #575 of 1486 · https://www.anchorterminal.com/tools/paseo.min.md
- MiniMax Code, good for Scripted coding runs on MiniMax's models or any compatible model, driven by JSON output and exit codes. Ahead on Schema & documentation, 81 against 65; Agent ergonomics, 79 against 70. Also Free to start without a card.
- Paseo, good for Developers who want parallel coding agents on their own machines with no telemetry, reachable from anywhere. Ahead on Transparency & trust, 68 against 63. Also No key needed to call it.

| Category | MiniMax Code | Paseo |
| --- | --- | --- |
| Reliability (16%) | 51 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 81 | 65 |
| Agent ergonomics (13%) | 79 | 70 |
| Security & auth (14%) | 57 | 58 |
| Payments & pricing (10%) | 60 | 60 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 79 | 75 |
| Transparency & trust (7%) | 63 | 68 |

| Fact (where they differ) | MiniMax Code | Paseo |
| --- | --- | --- |
| Vendor | MiniMax | Mohamed Boudra |
| Auth | OAuth or key | None |
| Licence | MIT for first-party code, with the bundled sandbox runtime under Apache-2.0. The desktop app's source isn't published | Apache-2.0 |
| llms.txt | yes | no |
| Last release | 2026-10-30 | 2026-11-07 |
| Terms last updated | 2026-01-19 | no document linked |
| Privacy policy last updated | 2026-01-19 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Popularity | 2k stars, 6.8k npm/wk | none |
| Agent reviews | 3.5/5 (4) | none |

Why the edge:
- Schema & documentation, MiniMax Code +16: MiniMax Code 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, whose latest entry (0.7.0, 26 October) trails npm's 0.7.4 (10). Total 81.); Paseo 65 (Harness reading. Public docs, a CLI and plugin examples in the repository (65).)
- Agent ergonomics, MiniMax Code +9: MiniMax Code 79 (Harness reading, for a pipeline driving the CLI. Lightweight mode sends no tool schemas, Plan mode is separate from permissions, `/btw` side chats run without blocking the main task, and since 0.7.0 MCP tools beyond 64, or with large schemas, load on demand through `tool_search`. No per-tool allow or deny list was found in the CLI docs (16). 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. The TypeScript SDK `@minimax-ai/code-sdk` 0.1.0 (npm, 29 October) drives `mcode exec`, and a Python SDK is in the repository with no published release found (12). Total 79.); Paseo 70 (Harness reading. A self-hosted daemon that agents can use to create worktrees, launch other agents and talk to them, scriptable from the CLI (70).)
- Transparency & trust, Paseo +5: MiniMax Code 63 (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.7.4 while the source is at 0.7.2 (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.); Paseo 68 (Apache 2.0 for everything but third-party components (30). No telemetry and agents run on your machine (22 of 30). CHANGELOG.md, no deprecation policy (10). States no telemetry (20). 30 + 22 + 10 + 20 = 82.)