MiniMax Code vs Verdent

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.

Verdent 35

Harness reading. MCP servers per project or globally, subagents, skills and rules, but no per-tool disabling or deferred loading found (10). No output-size, turn-limit or budget controls for a run were found beyond credit balances (5). No exit codes or error format, since there is no headless mode (3). Parallel workers in git worktrees and a review column make runs reviewable and reversible, with no resume by ID documented (10). No CLI, API or SDK. A pipeline can only reach Manager through a paired Telegram, Slack or Feishu bot (7). 10+5+3+10+7 = 35.

MiniMax Code 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.

Verdent 20

Harness reading of the published rubric, scored on the Verdent subscription the agent needs. No payment protocol (0). Plan prices from $5 a month, top-up prices and the credit value of about $0.059 are public without a login (20). Free Mode and the free trial ended on 29 October 2026, so there is no free tier (0). A person signs up in a browser (0). 0+20+0+0 = 20.

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.

Verdent 55

Framework reading for a harness. No schema for settings or output, only mcp.json examples in the standard mcpServers shape (5). Every current docs page has a Markdown twin at the same path with .md, though no llms.txt (10). The docs say when to use Agent Mode or Plan Mode and what Plan Mode can't do, but the Agent Mode page lists the actions that need approval only as "certain tool executions" and "destructive operations" (12). Modes and BYOA agent types are enumerated, permissions are not (5). Examples on the MCP, BYOA and messaging pages, and a recovery page, with no error codes (8). Version numbers and a dated public changelog (15). The archived 1.0 docs are still served beside the current ones. 5+10+12+5+8+15 = 55.

MiniMax Code 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 run in a release-audit workflow, and OSV lists no advisories for @minimax-ai/code or @minimax-ai/code-sdk. No security.txt (8). Total 57.

Verdent 33

Framework reading (telemetry defaults, approvals, guardrails, sandboxing). Conversation history and tool results go to Verdent's US servers and on to Azure, Bedrock or Vertex, with zero data retention stated for Vertex and Bedrock only. Event logging to log.verdent.ai has no documented opt-out. BYOA keys stay on the machine (10). Plan Mode is read-only, Agent Mode asks before destructive commands and edits outside scope, and workers are isolated by git worktree, but there is no sandbox or network control and the approval list isn't enumerated (9). No prompt-injection guidance found, while web search and fetch results enter the context (2). Usage history in the dashboard, no audit log found (5). A security page with a disclosure address and a five-day acknowledgement, SOC 2 and ISO/IEC 42001 being pursued rather than held, no security.txt and no bug bounty (7). 10+9+2+5+7 = 33.

MiniMax Code 79

0.7.4 on npm on 30 October 2026 (30). Every npm release from 0.1.0 on 14 August falls in the last 90 days, 62 of them by 15 October per the 19 October check (20). The clone has 167 commits since 3 August and 32 since 2 October, with fixes that cite issues, but pull requests are taken only from collaborators, and issue counts and reply times couldn't be read (11). An official TypeScript SDK, @minimax-ai/code-sdk 0.1.0, published on 29 October, and a Python SDK in the repository with no published release found. ACP ships inside the CLI (10). CI pins its GitHub Actions by commit, and the root package pins overrides for vulnerable dependencies (8). Total 79.

Verdent 61

Closed service. v2.18.0 on 29 October 2026, eight days before this check (30). More than three dated releases in the 90 days from 8 August, among them 2.10.0 to 2.18.0 (20). A dated public changelog, a support address, Discord and a subreddit, with no public tracker to read reply times (8). No official SDK or MCP server to keep current (0). No public packages or CI to judge (3). 30+20+8+0+3 = 61.

MiniMax Code 51

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 CI workflow runs on push and pull request with an Ubuntu, macOS and Windows matrix, beside release-audit, compatibility and Python SDK workflows. Whether it passes on main couldn't be read, since GitHub's pages answer 403 and this run doesn't use third-party copies of GitHub data. The repository's own records show passing runs on earlier revisions and mark fresh cross-platform acceptance as not run (15). Open issue counts and replies couldn't be read. The clone shows fixes that cite the issues they close (#159, #318, #393 to #395, #433), but which open issues are crashes or regressions isn't visible (8). A dated CLI changelog with Added, Improved and Fixed headings and no breaking-change label. Its latest entry is 0.7.0 (26 October) while npm's latest is 0.7.4 (30 October) (8). 0.7.x and called a source preview (0). Total 51.

Verdent 43

Local-package reading, as for the other closed-source harnesses. The desktop app installs from verdent.ai with macOS 11 or later and 64-bit Windows 10 and 11 stated, and the extension from the editor marketplaces, but not from a package registry (15). No public CI or test suite, since the source isn't published (0). No public issue tracker, every task runs through Verdent's servers, and no status page was found, so there is no readable record (5). A dated changelog by version, with the end of Free Mode called out in v2.18.0, but no breaking-change sections (8). 2.18.0, generally available (15). 15+0+5+8+15 = 43.