{ "data": { "a": { "slug": "deepseek-superagent", "name": "dsh-superagent (DeepSeek)", "vendor": "DeepSeek", "vendorUrl": "https://github.com/deepseek-ai/dsh-superagent-prototype", "kind": "harness", "category": "agent-harnesses", "summary": "dsh-superagent is DeepSeek's MIT-licensed research prototype of a proactive coding agent for one GitHub repository, run as a DeepSeek Harness bundle. A main Session admits requests from allowed people and parallel Executor Sessions work them into pull requests.", "url": "https://www.anchorterminal.com/tools/deepseek-superagent", "markdownUrl": "https://www.anchorterminal.com/tools/deepseek-superagent.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/deepseek-superagent.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/deepseek-superagent.json", "dns": "deepseek-superagent.grade.anchorterminal.com", "repo": "https://github.com/deepseek-ai/dsh-superagent-prototype", "license": "MIT", "transports": [], "packages": [], "auth": "pat", "authNotes": "No account with the project. The agent acts through a dedicated GitHub user account signed in to a `gh` wrapper with `auth login`, and optionally a Feishu bot through `lark-cli`. DSH needs a model provider key. The local Management API takes no credential and accepts only loopback requests with `x-orchestrator-request: 1`.", "pricing": "free", "pricingNotes": "Free and MIT, with nothing to buy. The operator pays the model provider DSH is set up with, usually DeepSeek's API, for a main Session and one Session per Ticket.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the README, SETUP.md or docs/000 to 008 (checked 2026-11-01).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-01" }, "docsUrl": "https://github.com/deepseek-ai/dsh-superagent-prototype/tree/main/docs", "capabilities": [ "agent.harness", "agent.multi-agent" ], "tags": [ "official", "harness", "coding-agent", "open-source", "mit", "typescript", "local", "free", "no-card", "pre-1.0", "preview", "telemetry-default-on" ], "lastRelease": "2026-10-31", "graded": true, "anchor": { "graded": true, "score": 42.1, "grade": "E", "agentReady": false, "rank": 1108, "ranked": true, "rankOf": 1251, "categoryRank": 41, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 34, "payments": 40, "reliability": 15, "schema": 61, "security": 33, "transparency": 52 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "The authorization design is careful, with allowed lists, Mandates and a Policy enforced in code, proactive work only recorded by default and auto-merge off. Executors run every command without approval under the operator's OS user, and the README calls it a research prototype with no release, changelog or security policy.", "bestFor": "Teams on github.com that want a DeepSeek Harness agent to turn allowed people's issue requests into pull requests, run on an isolated machine or OS account.", "strengths": [ "MIT licence, with nine numbered design and operations documents that state each rule, from admission to restart recovery", "Only listed GitHub logins can start work by default, and messages, comments and prompts cannot change the gate, which code enforces", "Proactive work starts in `observe` mode, which records what the agent would have done and accepts nothing", "The agent never enables auto-merge as its own account, and the default merge rule needs approvals and fewer than 200 changed lines", "Setup and worker shells drop environment variables named KEY, PASSWORD, SECRET or TOKEN, and git uses only the agent account's credentials" ], "weaknesses": [ "Executor and main Sessions run with `danger-full-access` as the operator's OS user, and the docs say a worker can read the operator's home directory", "The README calls it a research prototype, not an official DeepSeek product, at version 0.1.0 with no tag, release or changelog found", "Not on npm. Installing means a git clone, `pnpm build`, a pinned DSH release candidate, tmux and a dedicated GitHub user account", "The docs don't mention that DSH's shipped profiles upload the session log to DeepSeek with official API requests by default", "No SECURITY.md, security.txt or CI workflow found, and GitHub's issues and pull requests couldn't be read" ], "agentNotes": [ "Run it under a dedicated OS account holding only the agent's credentials. Executors run commands without approval and can read the operator's home directory", "Set `enabled: false` on the `session-log-deepseek` row of the `superagent` profile before using DeepSeek's official API on private code", "Keep the accept mode at `observe` and the allowed list short until the recorded Decisions look right", "Wait for `scripts/dsh-superagent status` to stop exiting 1 after any save that answers `restarting: true` before the next request", "Send `x-orchestrator-request: 1` and a loopback Host to the Management API, and send `revision` with each PUT, since a stale one gets 409" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 42.1 } ], "editorialScores": { "ergonomics": 67, "maintenance": 34, "payments": 40, "reliability": 15, "schema": 61, "security": 33, "transparency": 51 }, "provenanceScore": 52, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install -g @deepseek-ai/dsh@0.2.1-rc.3 \u0026\u0026 git clone https://github.com/deepseek-ai/dsh-superagent-prototype dsh-superagent \u0026\u0026 cd dsh-superagent \u0026\u0026 pnpm install \u0026\u0026 pnpm build \u0026\u0026 dsh superagent --from-default-profile web --dump-config \u003e /dev/null \u0026\u0026 dsh plugin --profile superagent add \"link:$PWD\"" }, "letme": { "capability": "https://letme.dev/agent.harness", "tool": "https://letme.dev/deepseek-superagent" }, "sameCompany": [ "deepseek-harness" ], "area": "frameworks", "provenance": { "legalEntity": "DeepSeek (the LICENSE names the DeepSeek Harness Team; DeepSeek Harness's terms name Hangzhou DeepSeek Artificial Intelligence Co., Ltd.)", "domain": "github.com", "domainRegistered": "", "endpointOnVendorDomain": null, "terms": "", "privacy": "https://www.deepseek.com/en/harness/privacy/", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-01", "notes": [ "The repository has no terms or privacy policy of its own. DeepSeek Harness's terms of use and privacy policy (both last updated 20 September 2026) name Hangzhou DeepSeek Artificial Intelligence Co., Ltd. and cover the harness it runs on. The README says the prototype is not an official DeepSeek product.", "package.json names `DeepSeek Harness Team \u003cteam@dsh.dev\u003e` as author. dsh.dev didn't resolve from our network on 1 November 2026.", "No SECURITY.md in the root or .github, and www.deepseek.com/.well-known/security.txt returned 404 on 1 November 2026.", "No CHANGELOG.md, tags or releases found. GitHub's web pages and API weren't reachable, so files were read on raw.githubusercontent.com and the commit history, stars and issues are unchecked." ], "score": 52 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/deepseek-superagent.json" }, "answer": "Kimi Code CLI scores 62.1 (B) on agent readiness against dsh-superagent (DeepSeek)'s 42.1 (E), and leads in every scored category.", "b": { "slug": "kimi-code-cli", "name": "Kimi Code CLI", "vendor": "Moonshot AI", "vendorUrl": "https://moonshotai.github.io/kimi-code/en/", "kind": "harness", "category": "agent-harnesses", "summary": "Open-source terminal coding agent from Moonshot AI that replaced the archived Python Kimi CLI. It runs Kimi, Anthropic, OpenAI or Gemini models, headless with `kimi -p`, as an ACP server, or behind a local REST server.", "url": "https://www.anchorterminal.com/tools/kimi-code-cli", "markdownUrl": "https://www.anchorterminal.com/tools/kimi-code-cli.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/kimi-code-cli.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/kimi-code-cli.json", "dns": "kimi-code-cli.grade.anchorterminal.com", "repo": "https://github.com/MoonshotAI/kimi-code", "license": "MIT", "transports": [], "packages": [ { "registry": "npm", "name": "@moonshot-ai/kimi-code" } ], "auth": "mixed", "authNotes": "Kimi Code OAuth (RFC 8628 device code through `/login` or `kimi login`) for a Kimi Code subscription, or a Kimi Platform API key. Anthropic, OpenAI, Gemini, Vertex AI and OpenAI-compatible providers take a key in `config.toml`. Provider keys in the shell are not read unless named through `api_key_env` or the `KIMI_MODEL_*` variables. OAuth tokens are stored in `~/.kimi-code/credentials/` with 0600 permissions.", "pricing": "free", "pricingNotes": "Free and MIT-licensed, with nothing to buy for the CLI. The owner pays the model provider. Kimi Platform API keys are billed pay-as-you-go per million tokens, and the Kimi Code subscription is sold as a Kimi membership plan whose prices render only with JavaScript and weren't read on 18 October 2026.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs or the 2.2.0 npm package (checked 2026-10-18).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 36761, "pypiWeekly": null, "asOf": "2026-10-18" }, "docsUrl": "https://moonshotai.github.io/kimi-code/en/", "llmsTxt": "https://moonshotai.github.io/kimi-code/llms.txt", "capabilities": [ "agent.harness", "agent.mcp-client", "agent.multi-agent" ], "tags": [ "official", "harness", "coding-agent", "cli", "open-source", "typescript", "mcp", "acp", "llms-txt", "telemetry-default-on", "no-sandbox", "free", "no-card", "local" ], "lastRelease": "2026-10-14", "graded": true, "anchor": { "graded": true, "score": 62.1, "grade": "B", "agentReady": false, "rank": 520, "ranked": true, "rankOf": 1251, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 72, "payments": 60, "reliability": 68, "schema": 85, "security": 45, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-18" }, "negative": -4, "negativeNotes": [ "2026-09-04. Version 0.41.0 fixed print mode (`kimi -p`) ignoring `KIMI_DISABLE_TELEMETRY`, so scripted runs sent telemetry after the user opted out. Fixed and stated in the changelog, -2. https://moonshotai.github.io/kimi-code/en/release-notes/changelog", "2026-09-23. Version 2.1.0 fixed file tools reaching outside the working directory through symlinks, repository git configuration running commands during background git operations, and project config applied before the workspace was trusted. Fixed and listed in the changelog, with no advisory published in OSV on 18 October 2026, -2. https://moonshotai.github.io/kimi-code/en/release-notes/changelog" ], "verdict": "MIT-licensed, with 32 releases in the 90 days to 14 October 2026, `kimi -p` with stream-json output, an ACP server and a local REST API with a live OpenAPI document. Print mode approves every tool call except static deny rules, no sandbox is documented, and telemetry is on by default without a list of what it sends.", "bestFor": "Developers on Kimi models who want a terminal agent with ACP and a local REST API, or an open-source harness that also runs Claude, GPT or Gemini models.", "strengths": [ "MIT-licensed, with a single-binary installer, npm and Homebrew core packages at 2.2.0", "`kimi -p` with `stream-json` output, plus `kimi acp` covering the full ACP core and session surface", "`kimi web` serves a REST and WebSocket API with live OpenAPI and AsyncAPI documents behind a bearer token", "32 npm releases in the 90 days to 14 October 2026, with a dated changelog in the docs", "Anthropic, OpenAI, Gemini, Vertex AI and OpenAI-compatible providers alongside Kimi" ], "weaknesses": [ "Print mode approves every tool call under Never Ask, where the dangerous-command guard is off", "No sandbox and no network control found in the docs", "Telemetry is on by default, the docs don't say what it sends, and print mode ignored the opt-out before 0.41.0", "No privacy page for the CLI, and the Kimi terms use content for training unless the user opts out by email", "Lifecycle hooks fail open, so a hook that errors or times out lets the tool call through" ], "agentNotes": [ "`kimi -p` approves every tool call. Add `[[permission.rules]]` deny entries and run it in a container, since no sandbox is documented", "Set `KIMI_LOOP_MAX_STEPS_PER_TURN` for unattended runs. Steps per turn are unlimited by default", "Pass the model with `KIMI_MODEL_NAME`, `KIMI_MODEL_API_KEY` and `KIMI_MODEL_PROVIDER_TYPE`. `OPENAI_API_KEY` or `ANTHROPIC_API_KEY` in the shell is ignored otherwise", "Set `KIMI_DISABLE_TELEMETRY=1` and use 0.41.0 or later, since earlier print-mode runs ignored it", "Install `@moonshot-ai/kimi-code` or the `kimi-code` formula. The `kimi-cli` and `kimi-code` packages on PyPI are the archived Python CLI" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.1 } ], "editorialScores": { "ergonomics": 71, "maintenance": 72, "payments": 60, "reliability": 68, "schema": 85, "security": 45, "transparency": 64 }, "provenanceScore": 59, "checked": { "categories": { "ergonomics": "2026-10-18", "maintenance": "2026-10-18", "payments": "2026-10-18", "reliability": "2026-10-18", "schema": "2026-10-18", "security": "2026-10-18", "transparency": "2026-10-18" }, "last": "2026-10-18", "lastMoved": "2026-10-30", "oldest": "2026-10-18", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash # or: npm install -g @moonshot-ai/kimi-code, or: brew install kimi-code", "headless": { "command": "kimi -p \"$TASK\" --output-format stream-json", "env": { "KIMI_DISABLE_TELEMETRY": "1", "KIMI_LOOP_MAX_STEPS_PER_TURN": "50", "KIMI_MODEL_API_KEY": "\u003ckey\u003e", "KIMI_MODEL_NAME": "\u003cmodel\u003e", "KIMI_MODEL_PROVIDER_TYPE": "kimi" } } }, "letme": { "capability": "https://letme.dev/agent.harness", "tool": "https://letme.dev/kimi-code-cli" }, "area": "frameworks", "provenance": { "legalEntity": "Moonshot AI (the global Kimi terms name NOVASCENT PRIVATE LIMITED, Singapore)", "domain": "moonshotai.github.io", "domainRegistered": "", "endpointOnVendorDomain": null, "terms": "https://www.kimi.ai/user/agreement/modelUse?version=v2", "privacy": "https://www.kimi.ai/user/agreement/userPrivacy?version=v2", "statusPage": "", "changelog": "https://moonshotai.github.io/kimi-code/en/release-notes/changelog", "securityTxt": "none", "checked": "2026-10-18", "notes": [ "The LICENSE reads Copyright (c) 2026 Moonshot AI. The Kimi terms (effective 13 August 2026) and privacy policy (last updated 13 August 2026), linked from the Kimi Code page on kimi.ai, name NOVASCENT PRIVATE LIMITED, a company registered in Singapore, as the provider. Neither names the CLI.", "The docs are on GitHub Pages and carry no terms or privacy page of their own. The Kimi Platform has separate terms and a privacy policy for API keys at platform.kimi.ai/docs/agreement.", "kimi.com, kimi.ai and moonshot.ai each answered /.well-known/security.txt with an HTML page, so no security.txt was found. SECURITY.md names private GitHub advisories and code@moonshot.ai." ], "score": 59 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/kimi-code-cli.json", "live": { "slug": "kimi-code-cli", "versions": [ { "registry": "github", "name": "MoonshotAI/kimi-code", "version": "@moonshot-ai/kimi-code@2.4.1", "released": "2026-10-30", "seenAt": "2026-10-31T16:02:12.47924251Z" }, { "registry": "npm", "name": "@moonshot-ai/kimi-code", "version": "2.4.1", "seenAt": "2026-10-31T16:02:12.075756353Z" } ], "githubStars": 8075, "npmWeekly": 97810, "securityTxt": { "url": "https://moonshotai.github.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-31T15:40:36.44937014Z" }, "llmsTxt": { "url": "https://moonshotai.github.io/kimi-code/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-31T15:11:03.516457344Z" }, "domain": { "domain": "github.io", "checkedAt": "2026-10-25T13:54:29.184658481Z" }, "pages": [ { "url": "https://moonshotai.github.io/kimi-code/en/release-notes/changelog", "kind": "deprecations", "status": 200, "checkedAt": "2026-10-31T06:16:33.390397142Z", "changedAt": "2026-10-31T06:16:33.390397142Z", "fingerprint": "8e992d492b4c" }, { "url": "https://www.kimi.ai/user/agreement/userPrivacy?version=v2", "kind": "privacy", "status": 200, "checkedAt": "2026-10-31T06:28:57.122454393Z", "changedAt": "2026-10-24T02:33:16.472023693Z", "fingerprint": "e735a31befb7" }, { "url": "https://www.kimi.ai/user/agreement/modelUse?version=v2", "kind": "terms", "status": 200, "checkedAt": "2026-10-31T06:28:54.500691478Z", "changedAt": "2026-10-24T02:33:13.953797656Z", "fingerprint": "a067685cfb90" } ], "github": { "repo": "moonshotai/kimi-code", "checkedAt": "2026-10-26T07:48:01.844605675Z", "stars": 8022, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-26T07:37:30Z", "openIssues": 1171, "openPRs": 482, "issuesOpened90d": 870, "issuesClosed90d": 210, "prsMerged90d": 765, "ci": { "branch": "main", "runs": 50, "success": 43, "failure": 4, "other": 3, "latest": "success", "latestAt": "2026-10-26T07:29:54Z" }, "replies": { "sampled": 11, "unanswered": 11 } }, "updatedAt": "2026-10-31T16:02:12.47924251Z" } }, "edges": [ { "by": 53, "category": "reliability", "leads": "kimi-code-cli", "name": "Reliability", "reasons": { "a": "Local-package reading, since it runs as a DSH bundle on the operator's machine. Not published to npm (`private: true` in package.json, and the registry has no `dsh-superagent`). It installs from a git clone with `pnpm install \u0026\u0026 pnpm build` on top of `@deepseek-ai/dsh@0.2.1-rc.3`, with Node 22.19+ or 24+, git 2.32+, Python 3.8+, tmux and gh 2.48+ stated, so half credit (10). A vitest suite of about 25 spec files is listed in docs/007, and `pnpm check` runs the typecheck, tests and build. Two spec files were read on raw.githubusercontent.com. No CI workflow was found at five common paths under .github/workflows, and the directory couldn't be listed (5). Open issues couldn't be read, because github.com and api.github.com weren't reachable from our network. Unchecked, so scored absent (0). Version 0.1.0 with no tag, release or changelog found, so no semver record (0). A research prototype, not stable (0).", "b": "Local-package reading. An install script that verifies a checksum, npm `@moonshot-ai/kimi-code` with Node 22.19.0 or newer stated, and Homebrew core at 2.2.0, for macOS, Linux and Windows (20). A public CI workflow runs the build, a smoke test, sharded tests on Linux, tests on Windows, lint and typecheck. GitHub refused our requests, so whether it passes on main wasn't checked (15). Read on 18 October through shields.io counts, 1.1k issues are open against 391 closed and 467 pull requests open against 2.3k closed, in a repository whose first commit was on 22 May 2026. Which of the open issues are crashes or regressions, and how fast they are answered, couldn't be read, so the line scores the backlog alone (8). Changesets changelog with Major, Minor and Patch headings and a Breaking note in 0.28.0, but 2.0.0's only major change was a new slash command, and 2.2.0 made configs with `executor = \"kaos\"` fail validation in a minor release (10). 2.2.0, past 1.0 (15)." }, "scores": { "a": 15, "b": 68 } }, { "by": 38, "category": "maintenance", "leads": "kimi-code-cli", "name": "Maintenance \u0026 community", "reasons": { "a": "Published on 31 October 2026, within 30 days, read as the last published change since no tag or release was found (30). One publication, so not three releases in 90 days (0). Issues, pull requests and Discussions couldn't be read, and the README frames the code as a reference prototype adapted from an internal version (0). No official SDK or registry entry (0). Exact dependency pins and a lockfile, but no CI workflow found, and the docs pin DSH 0.2.1-rc.3 (23 October 2026) while npm `latest` is 0.2.1-rc.5 (29 October 2026) (4).", "b": "2.2.0 on 14 October 2026 (30). 32 releases on npm in the 90 days to 14 October (20). Pull requests are closed at pace, 2.3k closed against 467 open, and the changelog credits merged pull requests up to #4159 from many contributors, with 742 commits in the 90 days to 18 October. Issues lag, with 1.1k open against 391 closed, and reply times couldn't be read (11). No SDK packages. The ACP server and REST API ship inside the CLI, and Homebrew core is current at 2.2.0 (5). CI with a frozen lockfile, lint and a dependency check (sherif), with no Dependabot file found and the pass state unchecked (6)." }, "scores": { "a": 34, "b": 72 } }, { "by": 24, "category": "schema", "leads": "kimi-code-cli", "name": "Schema \u0026 documentation", "reasons": { "a": "Framework reading, as for deepseek-harness. No OpenAPI or JSON Schema is published. docs/006 documents the Management API's routes, fields, block shapes and refusals in tables, and the code validates settings with zod (12). Markdown docs in the repository, readable raw, and a SETUP.md written for a coding agent. No llms.txt (5). Nine numbered documents read in order, each stating purpose, limits and what not to do, such as never rerunning the profile-creation command for an upgrade (17). Closed sets for accept mode (`off`, `observe`, `auto`), admission cells, Source states, health states and `listen` (12). A worked curl example, refusals as 400, 404, 409 and 500 with `issues`, `setup` or `code`, a troubleshooting table and status exit codes 0 to 3 (13). package.json says 0.1.0 and pins an `engines.dsh` range, but no changelog or tags were found (2).", "b": "Framework reading. The `kimi web` server serves `/openapi.json` and `/asyncapi.json`, generated from its runtime validation schemas, but only from a running server behind auth, and the API is marked experimental. The ACP server's methods and capabilities are tabled (20). llms.txt indexes every page and each page is served as Markdown (10). The permission-mode, goal-mode and MCP pages say when to use each mode and what to avoid (16). The config reference gives type and default for each key, with enums for permission modes, output formats and rule decisions (13). Many examples, the server's error-code bands and ACP error codes are documented, but print-mode exit codes are documented only for goal runs (11). A dated changelog in the docs plus the technical changelog in the repository (15)." }, "scores": { "a": 61, "b": 85 } }, { "by": 20, "category": "payments", "leads": "kimi-code-cli", "name": "Payments \u0026 pricing", "reasons": { "a": "Self-hosted rule, as for the other open-source harnesses. No payment protocol (0). Free under MIT with nothing to buy (20). No card for the software (20). An agent can't get started alone, because the setup needs a person to create a dedicated GitHub user account, accept the repository invitation and run `auth login` for the wrappers, which SETUP.md lists as operator steps. 0, as the other harnesses that need an account were read (0). The model provider is a separate purchase.", "b": "Self-hosted rule. No payment protocol (0). The CLI is free under MIT with nothing to buy (20). No card or account is needed for the software, and any listed provider's key works (20). An agent can install it from npm and run it with `KIMI_MODEL_*` variables and no sign-up, given a model key (20). The Kimi Code subscription and Kimi Platform API usage are separate purchases." }, "scores": { "a": 40, "b": 60 } }, { "by": 12, "category": "security", "leads": "kimi-code-cli", "name": "Security \u0026 auth", "reasons": { "a": "Harness reading of the framework checklist, 30 for 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. The `superagent` profile is created from DSH's Web template, and DSH documents that shipped profiles mount `session-log-deepseek`, enabled by default, which adds the session log to each official DeepSeek API request, up to 8 MiB. dsh-superagent's docs don't mention it, and its Sessions read issue, pull request and chat text and the repository. Setup and worker shells drop variables named KEY, PASSWORD, SECRET or TOKEN, and `GH_TOKEN` and `GITHUB_TOKEN` are removed from git (8). Both presets run `danger-full-access` without approval as the operator's OS user. docs/006 says the account wrappers don't isolate the process, a worker can run programs by path and read the operator's home directory, and recommends a dedicated OS account. The gate, `observe` default, blocked commands and no auto-merge as the agent account narrow what it does, not what it can do (6). docs/002 says messages, comments and quoted documents are inputs to a decision and can't change allowed lists, rules or Mandates, bots can never make explicit requests, and prompt edits don't change the gate. Workers with full access still read untrusted Thread text, and no further guidance on that was found (7). Decisions are recorded with reasons, Ticket details show the Trigger, Decision, scope and Policy version, the host records the prompt revisions each Session used, and every GitHub message starts with an automated-agent line by default (12). No SECURITY.md (404 at the root and in .github), no security.txt on www.deepseek.com (404), no bug bounty or advisory found. NVD has no record for the prototype. The CVEs against DSH itself are on the deepseek-harness listing (0).", "b": "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. OAuth tokens sit in 0600 files and shell keys aren't read unless named. Telemetry is on by default and, in the 2.2.0 package, sends events with a device ID, session ID and model name to telemetry-logs.kimi.com. Auto-update is on by default (14). Interactive sessions ask before edits and commands, and a dangerous-command guard covers `rm -rf` and similar, but `kimi -p` runs under Never Ask, where everything is approved and the guard is off, with only static deny rules left. No sandbox found, and hooks fail open (7). The MCP page warns about untrusted servers and project `.kimi-code/mcp.json` entries, and since 2.1.0 project config waits for workspace trust, but no prompt-injection guidance was found for fetched web pages (6). Sessions on disk, `kimi export`, the `kimi vis` session visualiser, a diagnostic log and hooks for auditing (11). SECURITY.md names private GitHub advisories and an email, supports only the latest version and gives no response time. No security.txt was found on kimi.com, kimi.ai or moonshot.ai, and OSV, the public mirror of the GitHub Advisory Database, lists no advisories for the package, though 2.1.0 shipped security fixes (7)." }, "scores": { "a": 33, "b": 45 } }, { "by": 10, "category": "transparency", "leads": "kimi-code-cli", "name": "Transparency \u0026 trust", "reasons": { "a": "MIT, Copyright (c) 2026 DeepSeek Harness Team (30). The prototype has no data statement of its own. DeepSeek Harness's privacy policy (last updated 20 September 2026) names Hangzhou DeepSeek Artificial Intelligence Co., Ltd., says session logs are collected with official model services and may be used to train models with a right to opt out, and says custom model services aren't stored server-side. It agrees with DSH's session-log README, but neither is referred to from the prototype (12). No deprecation policy. The README says the published code differs from DeepSeek's internal version, and docs/006 warns that database migrations are one-way (3). Telemetry and the session-log upload are disclosed with opt-outs in DSH's own reference pages, not in this repository (6).", "b": "MIT (30). The docs have no privacy page for the CLI. The Kimi terms (effective 13 August 2026, NOVASCENT PRIVATE LIMITED, Singapore) let Moonshot use content to train its services unless the user opts out by email, prospectively only, and the Kimi privacy policy says content is used for training. The Kimi Platform privacy policy keeps inputs while the account is active. Neither says which applies to CLI sessions (12). The `kimi server` tree prints a deprecation notice until the next major version, a table names each deprecated config key and the version that replaced it, and the Python Kimi CLI was archived with a migration guide, though its notice gives no date for when old installations stop working (13). Telemetry is documented as on, with a config key and an environment variable to turn it off, but what it collects isn't listed, and print mode ignored the opt-out until 0.41.0 (9)." }, "scores": { "a": 52, "b": 62 } } ], "facts": [ { "a": "Agent harness", "b": "Agent harness", "name": "Kind" }, { "a": "DeepSeek", "b": "Moonshot AI", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "Token", "b": "OAuth or key", "name": "Auth" }, { "a": "Free", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-31", "b": "2026-10-14", "name": "Last release" }, { "a": "no document linked", "b": "2026-08-13", "name": "Terms last updated" }, { "a": "2026-09-20", "b": "2026-08-13", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "yes, with an opt-out", "name": "Customer content may train models" }, { "a": "not read yet", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "37k npm/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Kimi Code CLI scores 62.1 (B) on agent readiness against dsh-superagent (DeepSeek)'s 42.1 (E), and leads in every scored category.", "question": "Which is better for AI agents, dsh-superagent (DeepSeek) or Kimi Code CLI?" }, { "answer": "Yes. dsh-superagent (DeepSeek) is open source (MIT). Kimi Code CLI is open source (MIT).", "question": "Are dsh-superagent (DeepSeek) and Kimi Code CLI open source?" } ], "goodFor": [ { "aheadOn": null, "also": [ "No incidents deducted, where Kimi Code CLI loses 4 points for them" ], "goodFor": "Teams on github.com that want a DeepSeek Harness agent to turn allowed people's issue requests into pull requests, run on an isolated machine or OS account.", "slug": "deepseek-superagent", "watchFor": "Executor and main Sessions run with `danger-full-access` as the operator's OS user, and the docs say a worker can read the operator's home directory" }, { "aheadOn": [ "Reliability, 68 against 15", "Schema \u0026 documentation, 85 against 61", "Security \u0026 auth, 45 against 33", "Payments \u0026 pricing, 60 against 40", "Maintenance \u0026 community, 72 against 34", "Transparency \u0026 trust, 62 against 52" ], "also": null, "goodFor": "Developers on Kimi models who want a terminal agent with ACP and a local REST API, or an open-source harness that also runs Claude, GPT or Gemini models.", "slug": "kimi-code-cli", "watchFor": "Print mode approves every tool call under Never Ask, where the dangerous-command guard is off" } ], "history": { "deepseek-superagent": null, "kimi-code-cli": [ { "causes": [ "method" ], "date": "2026-10-30", "delta": 0, "from": 62.1, "fromGrade": "B", "to": 62.1, "toGrade": "B" }, { "causes": [ "evidence" ], "date": "2026-10-27", "delta": 0, "from": 62.1, "fromGrade": "B", "to": 62.1, "toGrade": "B" } ] }, "job": { "capability": "agent.harness", "name": "Agent harnesses" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-deepseek-superagent.json", "title": "Agent Zero vs dsh-superagent (DeepSeek)", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-deepseek-superagent" }, { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-kimi-code-cli.json", "title": "Agent Zero vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/aider-vs-deepseek-superagent.json", "title": "Aider vs dsh-superagent (DeepSeek)", "url": "https://www.anchorterminal.com/compare/aider-vs-deepseek-superagent" }, { "json": "https://www.anchorterminal.com/compare/aider-vs-kimi-code-cli.json", "title": "Aider vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/aider-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/amp-vs-deepseek-superagent.json", "title": "Amp vs dsh-superagent (DeepSeek)", "url": "https://www.anchorterminal.com/compare/amp-vs-deepseek-superagent" }, { "json": "https://www.anchorterminal.com/compare/amp-vs-kimi-code-cli.json", "title": "Amp vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/amp-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/antigravity-cli-vs-deepseek-superagent.json", "title": "Antigravity CLI vs dsh-superagent (DeepSeek)", "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-deepseek-superagent" }, { "json": "https://www.anchorterminal.com/compare/antigravity-cli-vs-kimi-code-cli.json", "title": "Antigravity CLI vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/auggie-vs-deepseek-superagent.json", "title": "Auggie CLI vs dsh-superagent (DeepSeek)", "url": "https://www.anchorterminal.com/compare/auggie-vs-deepseek-superagent" }, { "json": "https://www.anchorterminal.com/compare/auggie-vs-kimi-code-cli.json", "title": "Auggie CLI vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/auggie-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/claude-code-vs-deepseek-superagent.json", "title": "Claude Code vs dsh-superagent (DeepSeek)", "url": "https://www.anchorterminal.com/compare/claude-code-vs-deepseek-superagent" }, { "json": "https://www.anchorterminal.com/compare/claude-code-vs-kimi-code-cli.json", "title": "Claude Code vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/claude-code-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/cline-vs-deepseek-superagent.json", "title": "Cline vs dsh-superagent (DeepSeek)", "url": "https://www.anchorterminal.com/compare/cline-vs-deepseek-superagent" }, { "json": "https://www.anchorterminal.com/compare/cline-vs-kimi-code-cli.json", "title": "Cline vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/cline-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-deepseek-superagent.json", "title": "Crush vs dsh-superagent (DeepSeek)", "url": "https://www.anchorterminal.com/compare/crush-vs-deepseek-superagent" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-kimi-code-cli.json", "title": "Crush vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/cursor-cli-vs-deepseek-superagent.json", "title": "Cursor CLI vs dsh-superagent (DeepSeek)", "url": "https://www.anchorterminal.com/compare/cursor-cli-vs-deepseek-superagent" }, { "json": "https://www.anchorterminal.com/compare/cursor-cli-vs-kimi-code-cli.json", "title": "Cursor CLI vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/cursor-cli-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-harness-vs-deepseek-superagent.json", "title": "DeepSeek Harness (dsh) vs dsh-superagent (DeepSeek)", "url": "https://www.anchorterminal.com/compare/deepseek-harness-vs-deepseek-superagent" }, { "json": "https://www.anchorterminal.com/compare/deepseek-harness-vs-kimi-code-cli.json", "title": "DeepSeek Harness (dsh) vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/deepseek-harness-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-devin.json", "title": "dsh-superagent (DeepSeek) vs Devin", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-devin" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-droid-cli.json", "title": "dsh-superagent (DeepSeek) vs Droid CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-droid-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-earendil-pi.json", "title": "dsh-superagent (DeepSeek) vs Pi", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-earendil-pi" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-gemini-cli.json", "title": "dsh-superagent (DeepSeek) vs Gemini CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-gemini-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-github-copilot-cli.json", "title": "dsh-superagent (DeepSeek) vs GitHub Copilot CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-github-copilot-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-goose.json", "title": "dsh-superagent (DeepSeek) vs goose", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-goose" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-harness2.json", "title": "dsh-superagent (DeepSeek) vs Harness²", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-harness2" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-harnessrouter.json", "title": "dsh-superagent (DeepSeek) vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-jules.json", "title": "dsh-superagent (DeepSeek) vs Jules", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-jules" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-junie.json", "title": "dsh-superagent (DeepSeek) vs Junie CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-junie" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kilo-code-cli.json", "title": "dsh-superagent (DeepSeek) vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli.json", "title": "dsh-superagent (DeepSeek) vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-mini-swe-agent.json", "title": "dsh-superagent (DeepSeek) vs mini-swe-agent", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-mini-swe-agent" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-minimax-code.json", "title": "dsh-superagent (DeepSeek) vs MiniMax Code", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-minimax-code" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-mistral-vibe-cli.json", "title": "dsh-superagent (DeepSeek) vs Mistral Vibe CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-mistral-vibe-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-muse-code.json", "title": "dsh-superagent (DeepSeek) vs Muse Code", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-muse-code" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-openai-codex.json", "title": "dsh-superagent (DeepSeek) vs OpenAI Codex", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-openai-codex" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-opencode.json", "title": "dsh-superagent (DeepSeek) vs OpenCode", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-opencode" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-openhands.json", "title": "dsh-superagent (DeepSeek) vs OpenHands", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-openhands" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-openmausbot.json", "title": "dsh-superagent (DeepSeek) vs OpenMausBot", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-openmausbot" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-prime-agent.json", "title": "dsh-superagent (DeepSeek) vs Prime Agent", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-prime-agent" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-qoder-cli.json", "title": "dsh-superagent (DeepSeek) vs Qoder CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-qoder-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-qwen-code.json", "title": "dsh-superagent (DeepSeek) vs Qwen Code", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-qwen-code" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-reflection-mirror.json", "title": "dsh-superagent (DeepSeek) vs Mirror CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-reflection-mirror" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-rovo-dev-cli.json", "title": "dsh-superagent (DeepSeek) vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-unstoppable.json", "title": "dsh-superagent (DeepSeek) vs Unstoppable", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-unstoppable" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-vibe-trading.json", "title": "dsh-superagent (DeepSeek) vs Vibe-Trading", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-vibe-trading" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-warp.json", "title": "dsh-superagent (DeepSeek) vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-warp" }, { "json": "https://www.anchorterminal.com/compare/devin-vs-kimi-code-cli.json", "title": "Devin vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/devin-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/droid-cli-vs-kimi-code-cli.json", "title": "Droid CLI vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/droid-cli-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/earendil-pi-vs-kimi-code-cli.json", "title": "Pi vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/earendil-pi-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/gemini-cli-vs-kimi-code-cli.json", "title": "Gemini CLI vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/gemini-cli-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-kimi-code-cli.json", "title": "GitHub Copilot CLI vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/goose-vs-kimi-code-cli.json", "title": "goose vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/goose-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/harness2-vs-kimi-code-cli.json", "title": "Harness² vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/harness2-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-kimi-code-cli.json", "title": "HarnessRouter vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/jules-vs-kimi-code-cli.json", "title": "Jules vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/jules-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/junie-vs-kimi-code-cli.json", "title": "Junie CLI vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/junie-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-kimi-code-cli.json", "title": "Kilo Code CLI vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-kiro-cli.json", "title": "Kimi Code CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-mini-swe-agent.json", "title": "Kimi Code CLI vs mini-swe-agent", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-mini-swe-agent" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-minimax-code.json", "title": "Kimi Code CLI vs MiniMax Code", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-minimax-code" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-mistral-vibe-cli.json", "title": "Kimi Code CLI vs Mistral Vibe CLI", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-mistral-vibe-cli" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-muse-code.json", "title": "Kimi Code CLI vs Muse Code", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-muse-code" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-openai-codex.json", "title": "Kimi Code CLI vs OpenAI Codex", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-openai-codex" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-opencode.json", "title": "Kimi Code CLI vs OpenCode", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-opencode" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-openhands.json", "title": "Kimi Code CLI vs OpenHands", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-openhands" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-openmausbot.json", "title": "Kimi Code CLI vs OpenMausBot", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-openmausbot" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-prime-agent.json", "title": "Kimi Code CLI vs Prime Agent", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-prime-agent" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-qoder-cli.json", "title": "Kimi Code CLI vs Qoder CLI", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-qoder-cli" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-qwen-code.json", "title": "Kimi Code CLI vs Qwen Code", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-qwen-code" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-reflection-mirror.json", "title": "Kimi Code CLI vs Mirror CLI", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-reflection-mirror" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-rovo-dev-cli.json", "title": "Kimi Code CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-unstoppable.json", "title": "Kimi Code CLI vs Unstoppable", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-unstoppable" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-vibe-trading.json", "title": "Kimi Code CLI vs Vibe-Trading", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-vibe-trading" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-warp.json", "title": "Kimi Code CLI vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-warp" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-deepseek-superagent.json", "title": "Clawboo vs dsh-superagent (DeepSeek)", "url": "https://www.anchorterminal.com/compare/clawboo-vs-deepseek-superagent" }, { "json": "https://www.anchorterminal.com/compare/clawboo-vs-kimi-code-cli.json", "title": "Clawboo vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/clawboo-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/cli-manager-vs-deepseek-superagent.json", "title": "CLI Manager vs dsh-superagent (DeepSeek)", "url": "https://www.anchorterminal.com/compare/cli-manager-vs-deepseek-superagent" }, { "json": "https://www.anchorterminal.com/compare/cli-manager-vs-kimi-code-cli.json", "title": "CLI Manager vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/cli-manager-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-harness-autonomous.json", "title": "dsh-superagent (DeepSeek) vs Harness", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-harness-autonomous" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-paperclip.json", "title": "dsh-superagent (DeepSeek) vs Paperclip", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-paperclip" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-parallax-agents.json", "title": "dsh-superagent (DeepSeek) vs Parallax", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-parallax-agents" }, { "json": "https://www.anchorterminal.com/compare/harness-autonomous-vs-kimi-code-cli.json", "title": "Harness vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/harness-autonomous-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-paperclip.json", "title": "Kimi Code CLI vs Paperclip", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-paperclip" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-parallax-agents.json", "title": "Kimi Code CLI vs Parallax", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-parallax-agents" } ], "panel": null, "scores": [ { "by": 53, "deepseek-superagent": 15, "edge": "kimi-code-cli", "key": "reliability", "kimi-code-cli": 68, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 24, "deepseek-superagent": 61, "edge": "kimi-code-cli", "key": "schema", "kimi-code-cli": 85, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 4, "deepseek-superagent": 67, "edge": "kimi-code-cli", "key": "ergonomics", "kimi-code-cli": 71, "name": "Agent ergonomics", "weight": 13 }, { "by": 12, "deepseek-superagent": 33, "edge": "kimi-code-cli", "key": "security", "kimi-code-cli": 45, "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "deepseek-superagent": 40, "edge": "kimi-code-cli", "key": "payments", "kimi-code-cli": 60, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 38, "deepseek-superagent": 34, "edge": "kimi-code-cli", "key": "maintenance", "kimi-code-cli": 72, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 10, "deepseek-superagent": 52, "edge": "kimi-code-cli", "key": "transparency", "kimi-code-cli": 62, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Kimi Code CLI scores 62.1 (B) on agent readiness against dsh-superagent (DeepSeek)'s 42.1 (E), and leads in every scored category. Both do agent harnesses.", "tasks": null, "tutorials": [], "verdicts": { "deepseek-superagent": "The authorization design is careful, with allowed lists, Mandates and a Policy enforced in code, proactive work only recorded by default and auto-merge off. Executors run every command without approval under the operator's OS user, and the README calls it a research prototype with no release, changelog or security policy.", "kimi-code-cli": "MIT-licensed, with 32 releases in the 90 days to 14 October 2026, `kimi -p` with stream-json output, an ACP server and a local REST API with a live OpenAPI document. Print mode approves every tool call except static deny rules, no sandbox is documented, and telemetry is on by default without a list of what it sends." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kimi-code-cli", "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kimi-code-cli.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kimi-code-cli.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kimi-code-cli.min.md" }, "markdown": "Kimi Code CLI scores 62.1 (B) on agent readiness against dsh-superagent (DeepSeek)'s 42.1 (E), and leads in every scored category. Both do agent harnesses.\n\n- dsh-superagent (DeepSeek): grade E, 42.1/100, rank #1108 of 1251. Markdown https://www.anchorterminal.com/tools/deepseek-superagent.md · JSON https://www.anchorterminal.com/api/v1/tools/deepseek-superagent.json\n- Kimi Code CLI: grade B, 62.1/100, rank #520 of 1251. Markdown https://www.anchorterminal.com/tools/kimi-code-cli.md · JSON https://www.anchorterminal.com/api/v1/tools/kimi-code-cli.json\n- Best agent harnesses and coding agents: https://www.anchorterminal.com/best/agent-harnesses/index.md\n- All 955 harnesses comparisons: https://www.anchorterminal.com/compare/agent-harnesses/index.md\n\n## Which one, for what\n\n### dsh-superagent (DeepSeek) (E)\n\nGood for: Teams on github.com that want a DeepSeek Harness agent to turn allowed people's issue requests into pull requests, run on an isolated machine or OS account.\n\nAlso in its favour:\n- No incidents deducted, where Kimi Code CLI loses 4 points for them\n\nWatch for: Executor and main Sessions run with `danger-full-access` as the operator's OS user, and the docs say a worker can read the operator's home directory\n\n### Kimi Code CLI (B)\n\nGood for: Developers on Kimi models who want a terminal agent with ACP and a local REST API, or an open-source harness that also runs Claude, GPT or Gemini models.\n\nAhead on:\n- Reliability, 68 against 15\n- Schema \u0026 documentation, 85 against 61\n- Security \u0026 auth, 45 against 33\n- Payments \u0026 pricing, 60 against 40\n- Maintenance \u0026 community, 72 against 34\n- Transparency \u0026 trust, 62 against 52\n\nWatch for: Print mode approves every tool call under Never Ask, where the dangerous-command guard is off\n\n\n## Why the edge\n\n### Reliability: Kimi Code CLI +53\n\n- dsh-superagent (DeepSeek) (15): Local-package reading, since it runs as a DSH bundle on the operator's machine. Not published to npm (`private: true` in package.json, and the registry has no `dsh-superagent`). It installs from a git clone with `pnpm install \u0026\u0026 pnpm build` on top of `@deepseek-ai/dsh@0.2.1-rc.3`, with Node 22.19+ or 24+, git 2.32+, Python 3.8+, tmux and gh 2.48+ stated, so half credit (10). A vitest suite of about 25 spec files is listed in docs/007, and `pnpm check` runs the typecheck, tests and build. Two spec files were read on raw.githubusercontent.com. No CI workflow was found at five common paths under .github/workflows, and the directory couldn't be listed (5). Open issues couldn't be read, because github.com and api.github.com weren't reachable from our network. Unchecked, so scored absent (0). Version 0.1.0 with no tag, release or changelog found, so no semver record (0). A research prototype, not stable (0).\n- Kimi Code CLI (68): Local-package reading. An install script that verifies a checksum, npm `@moonshot-ai/kimi-code` with Node 22.19.0 or newer stated, and Homebrew core at 2.2.0, for macOS, Linux and Windows (20). A public CI workflow runs the build, a smoke test, sharded tests on Linux, tests on Windows, lint and typecheck. GitHub refused our requests, so whether it passes on main wasn't checked (15). Read on 18 October through shields.io counts, 1.1k issues are open against 391 closed and 467 pull requests open against 2.3k closed, in a repository whose first commit was on 22 May 2026. Which of the open issues are crashes or regressions, and how fast they are answered, couldn't be read, so the line scores the backlog alone (8). Changesets changelog with Major, Minor and Patch headings and a Breaking note in 0.28.0, but 2.0.0's only major change was a new slash command, and 2.2.0 made configs with `executor = \"kaos\"` fail validation in a minor release (10). 2.2.0, past 1.0 (15).\n\n### Maintenance \u0026 community: Kimi Code CLI +38\n\n- dsh-superagent (DeepSeek) (34): Published on 31 October 2026, within 30 days, read as the last published change since no tag or release was found (30). One publication, so not three releases in 90 days (0). Issues, pull requests and Discussions couldn't be read, and the README frames the code as a reference prototype adapted from an internal version (0). No official SDK or registry entry (0). Exact dependency pins and a lockfile, but no CI workflow found, and the docs pin DSH 0.2.1-rc.3 (23 October 2026) while npm `latest` is 0.2.1-rc.5 (29 October 2026) (4).\n- Kimi Code CLI (72): 2.2.0 on 14 October 2026 (30). 32 releases on npm in the 90 days to 14 October (20). Pull requests are closed at pace, 2.3k closed against 467 open, and the changelog credits merged pull requests up to #4159 from many contributors, with 742 commits in the 90 days to 18 October. Issues lag, with 1.1k open against 391 closed, and reply times couldn't be read (11). No SDK packages. The ACP server and REST API ship inside the CLI, and Homebrew core is current at 2.2.0 (5). CI with a frozen lockfile, lint and a dependency check (sherif), with no Dependabot file found and the pass state unchecked (6).\n\n### Schema \u0026 documentation: Kimi Code CLI +24\n\n- dsh-superagent (DeepSeek) (61): Framework reading, as for deepseek-harness. No OpenAPI or JSON Schema is published. docs/006 documents the Management API's routes, fields, block shapes and refusals in tables, and the code validates settings with zod (12). Markdown docs in the repository, readable raw, and a SETUP.md written for a coding agent. No llms.txt (5). Nine numbered documents read in order, each stating purpose, limits and what not to do, such as never rerunning the profile-creation command for an upgrade (17). Closed sets for accept mode (`off`, `observe`, `auto`), admission cells, Source states, health states and `listen` (12). A worked curl example, refusals as 400, 404, 409 and 500 with `issues`, `setup` or `code`, a troubleshooting table and status exit codes 0 to 3 (13). package.json says 0.1.0 and pins an `engines.dsh` range, but no changelog or tags were found (2).\n- Kimi Code CLI (85): Framework reading. The `kimi web` server serves `/openapi.json` and `/asyncapi.json`, generated from its runtime validation schemas, but only from a running server behind auth, and the API is marked experimental. The ACP server's methods and capabilities are tabled (20). llms.txt indexes every page and each page is served as Markdown (10). The permission-mode, goal-mode and MCP pages say when to use each mode and what to avoid (16). The config reference gives type and default for each key, with enums for permission modes, output formats and rule decisions (13). Many examples, the server's error-code bands and ACP error codes are documented, but print-mode exit codes are documented only for goal runs (11). A dated changelog in the docs plus the technical changelog in the repository (15).\n\n### Payments \u0026 pricing: Kimi Code CLI +20\n\n- dsh-superagent (DeepSeek) (40): Self-hosted rule, as for the other open-source harnesses. No payment protocol (0). Free under MIT with nothing to buy (20). No card for the software (20). An agent can't get started alone, because the setup needs a person to create a dedicated GitHub user account, accept the repository invitation and run `auth login` for the wrappers, which SETUP.md lists as operator steps. 0, as the other harnesses that need an account were read (0). The model provider is a separate purchase.\n- Kimi Code CLI (60): Self-hosted rule. No payment protocol (0). The CLI is free under MIT with nothing to buy (20). No card or account is needed for the software, and any listed provider's key works (20). An agent can install it from npm and run it with `KIMI_MODEL_*` variables and no sign-up, given a model key (20). The Kimi Code subscription and Kimi Platform API usage are separate purchases.\n\n### Security \u0026 auth: Kimi Code CLI +12\n\n- dsh-superagent (DeepSeek) (33): Harness reading of the framework checklist, 30 for 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. The `superagent` profile is created from DSH's Web template, and DSH documents that shipped profiles mount `session-log-deepseek`, enabled by default, which adds the session log to each official DeepSeek API request, up to 8 MiB. dsh-superagent's docs don't mention it, and its Sessions read issue, pull request and chat text and the repository. Setup and worker shells drop variables named KEY, PASSWORD, SECRET or TOKEN, and `GH_TOKEN` and `GITHUB_TOKEN` are removed from git (8). Both presets run `danger-full-access` without approval as the operator's OS user. docs/006 says the account wrappers don't isolate the process, a worker can run programs by path and read the operator's home directory, and recommends a dedicated OS account. The gate, `observe` default, blocked commands and no auto-merge as the agent account narrow what it does, not what it can do (6). docs/002 says messages, comments and quoted documents are inputs to a decision and can't change allowed lists, rules or Mandates, bots can never make explicit requests, and prompt edits don't change the gate. Workers with full access still read untrusted Thread text, and no further guidance on that was found (7). Decisions are recorded with reasons, Ticket details show the Trigger, Decision, scope and Policy version, the host records the prompt revisions each Session used, and every GitHub message starts with an automated-agent line by default (12). No SECURITY.md (404 at the root and in .github), no security.txt on www.deepseek.com (404), no bug bounty or advisory found. NVD has no record for the prototype. The CVEs against DSH itself are on the deepseek-harness listing (0).\n- Kimi Code CLI (45): 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. OAuth tokens sit in 0600 files and shell keys aren't read unless named. Telemetry is on by default and, in the 2.2.0 package, sends events with a device ID, session ID and model name to telemetry-logs.kimi.com. Auto-update is on by default (14). Interactive sessions ask before edits and commands, and a dangerous-command guard covers `rm -rf` and similar, but `kimi -p` runs under Never Ask, where everything is approved and the guard is off, with only static deny rules left. No sandbox found, and hooks fail open (7). The MCP page warns about untrusted servers and project `.kimi-code/mcp.json` entries, and since 2.1.0 project config waits for workspace trust, but no prompt-injection guidance was found for fetched web pages (6). Sessions on disk, `kimi export`, the `kimi vis` session visualiser, a diagnostic log and hooks for auditing (11). SECURITY.md names private GitHub advisories and an email, supports only the latest version and gives no response time. No security.txt was found on kimi.com, kimi.ai or moonshot.ai, and OSV, the public mirror of the GitHub Advisory Database, lists no advisories for the package, though 2.1.0 shipped security fixes (7).\n\n### Transparency \u0026 trust: Kimi Code CLI +10\n\n- dsh-superagent (DeepSeek) (52): MIT, Copyright (c) 2026 DeepSeek Harness Team (30). The prototype has no data statement of its own. DeepSeek Harness's privacy policy (last updated 20 September 2026) names Hangzhou DeepSeek Artificial Intelligence Co., Ltd., says session logs are collected with official model services and may be used to train models with a right to opt out, and says custom model services aren't stored server-side. It agrees with DSH's session-log README, but neither is referred to from the prototype (12). No deprecation policy. The README says the published code differs from DeepSeek's internal version, and docs/006 warns that database migrations are one-way (3). Telemetry and the session-log upload are disclosed with opt-outs in DSH's own reference pages, not in this repository (6).\n- Kimi Code CLI (62): MIT (30). The docs have no privacy page for the CLI. The Kimi terms (effective 13 August 2026, NOVASCENT PRIVATE LIMITED, Singapore) let Moonshot use content to train its services unless the user opts out by email, prospectively only, and the Kimi privacy policy says content is used for training. The Kimi Platform privacy policy keeps inputs while the account is active. Neither says which applies to CLI sessions (12). The `kimi server` tree prints a deprecation notice until the next major version, a table names each deprecated config key and the version that replaced it, and the Python Kimi CLI was archived with a migration guide, though its notice gives no date for when old installations stop working (13). Telemetry is documented as on, with a config key and an environment variable to turn it off, but what it collects isn't listed, and print mode ignored the opt-out until 0.41.0 (9).\n\n## Score by category\n\n| Category | Weight | dsh-superagent (DeepSeek) | Kimi Code CLI | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 68 | Kimi Code CLI +53 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 61 | 85 | Kimi Code CLI +24 |\n| Agent ergonomics | 13% (16.2 this run) | 67 | 71 | Kimi Code CLI +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 33 | 45 | Kimi Code CLI +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 60 | Kimi Code CLI +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 34 | 72 | Kimi Code CLI +38 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 52 | 62 | Kimi Code CLI +10 |\n| Negative events | ≤15 | 0 | -4 | |\n| **Total** | | **42.1 · E** | **62.1 · B** | |\n\n## Facts side by side\n\n| Fact | dsh-superagent (DeepSeek) | Kimi Code CLI |\n| --- | --- | --- |\n| Kind | Agent harness | Agent harness |\n| Vendor | DeepSeek | Moonshot AI |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | Token | OAuth or key |\n| Pricing | Free | Free |\n| x402 | no | no |\n| Licence | MIT | MIT |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-31 | 2026-10-14 |\n| Terms last updated | no document linked | 2026-08-13 |\n| Privacy policy last updated | 2026-09-20 | 2026-08-13 |\n| Customer content may train models | not read yet | yes, with an opt-out |\n| Terms restrict automated access | not read yet | yes |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | yes |\n| Popularity | none | 37k npm/wk |\n| Agent reviews | none | 3/5 (4) |\n\n## How the scores have moved\n\n### dsh-superagent (DeepSeek)\n\nNo score change since it was listed.\n\n### Kimi Code CLI\n\n- no change on 30 October 2026: checklist\n- no change on 27 October 2026: new evidence\n\n## Verdicts\n\n**dsh-superagent (DeepSeek).** The authorization design is careful, with allowed lists, Mandates and a Policy enforced in code, proactive work only recorded by default and auto-merge off. Executors run every command without approval under the operator's OS user, and the README calls it a research prototype with no release, changelog or security policy.\n\n**Kimi Code CLI.** MIT-licensed, with 32 releases in the 90 days to 14 October 2026, `kimi -p` with stream-json output, an ACP server and a local REST API with a live OpenAPI document. Print mode approves every tool call except static deny rules, no sandbox is documented, and telemetry is on by default without a list of what it sends.\n\n## Before you call either\n\n### dsh-superagent (DeepSeek)\n\n1. Run it under a dedicated OS account holding only the agent's credentials. Executors run commands without approval and can read the operator's home directory\n2. Set `enabled: false` on the `session-log-deepseek` row of the `superagent` profile before using DeepSeek's official API on private code\n3. Keep the accept mode at `observe` and the allowed list short until the recorded Decisions look right\n4. Wait for `scripts/dsh-superagent status` to stop exiting 1 after any save that answers `restarting: true` before the next request\n5. Send `x-orchestrator-request: 1` and a loopback Host to the Management API, and send `revision` with each PUT, since a stale one gets 409\n\n### Kimi Code CLI\n\n1. `kimi -p` approves every tool call. Add `[[permission.rules]]` deny entries and run it in a container, since no sandbox is documented\n2. Set `KIMI_LOOP_MAX_STEPS_PER_TURN` for unattended runs. Steps per turn are unlimited by default\n3. Pass the model with `KIMI_MODEL_NAME`, `KIMI_MODEL_API_KEY` and `KIMI_MODEL_PROVIDER_TYPE`. `OPENAI_API_KEY` or `ANTHROPIC_API_KEY` in the shell is ignored otherwise\n4. Set `KIMI_DISABLE_TELEMETRY=1` and use 0.41.0 or later, since earlier print-mode runs ignored it\n5. Install `@moonshot-ai/kimi-code` or the `kimi-code` formula. The `kimi-cli` and `kimi-code` packages on PyPI are the archived Python CLI\n\n## Questions\n\n### Which is better for AI agents, dsh-superagent (DeepSeek) or Kimi Code CLI?\n\nKimi Code CLI scores 62.1 (B) on agent readiness against dsh-superagent (DeepSeek)'s 42.1 (E), and leads in every scored category.\n\n### Are dsh-superagent (DeepSeek) and Kimi Code CLI open source?\n\nYes. dsh-superagent (DeepSeek) is open source (MIT). Kimi Code CLI is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/deepseek-superagent-vs-kimi-code-cli.json, and with the fewest tokens: https://www.anchorterminal.com/compare/deepseek-superagent-vs-kimi-code-cli.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"deepseek-superagent\", \"b\": \"kimi-code-cli\"}`. From a terminal: `anchor compare deepseek-superagent kimi-code-cli`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/deepseek-superagent.json and https://www.anchorterminal.com/api/v1/tools/kimi-code-cli.json\n\n## Other comparisons with dsh-superagent (DeepSeek) or Kimi Code CLI\n\n- [Agent Zero vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/agent-zero-vs-deepseek-superagent.md)\n- [Agent Zero vs Kimi Code CLI](https://www.anchorterminal.com/compare/agent-zero-vs-kimi-code-cli.md)\n- [Aider vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/aider-vs-deepseek-superagent.md)\n- [Aider vs Kimi Code CLI](https://www.anchorterminal.com/compare/aider-vs-kimi-code-cli.md)\n- [Amp vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/amp-vs-deepseek-superagent.md)\n- [Amp vs Kimi Code CLI](https://www.anchorterminal.com/compare/amp-vs-kimi-code-cli.md)\n- [Antigravity CLI vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/antigravity-cli-vs-deepseek-superagent.md)\n- [Antigravity CLI vs Kimi Code CLI](https://www.anchorterminal.com/compare/antigravity-cli-vs-kimi-code-cli.md)\n- [Auggie CLI vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/auggie-vs-deepseek-superagent.md)\n- [Auggie CLI vs Kimi Code CLI](https://www.anchorterminal.com/compare/auggie-vs-kimi-code-cli.md)\n- [Claude Code vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/claude-code-vs-deepseek-superagent.md)\n- [Claude Code vs Kimi Code CLI](https://www.anchorterminal.com/compare/claude-code-vs-kimi-code-cli.md)\n- [Cline vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/cline-vs-deepseek-superagent.md)\n- [Cline vs Kimi Code CLI](https://www.anchorterminal.com/compare/cline-vs-kimi-code-cli.md)\n- [Crush vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/crush-vs-deepseek-superagent.md)\n- [Crush vs Kimi Code CLI](https://www.anchorterminal.com/compare/crush-vs-kimi-code-cli.md)\n- [Cursor CLI vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/cursor-cli-vs-deepseek-superagent.md)\n- [Cursor CLI vs Kimi Code CLI](https://www.anchorterminal.com/compare/cursor-cli-vs-kimi-code-cli.md)\n- [DeepSeek Harness (dsh) vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/deepseek-harness-vs-deepseek-superagent.md)\n- [DeepSeek Harness (dsh) vs Kimi Code CLI](https://www.anchorterminal.com/compare/deepseek-harness-vs-kimi-code-cli.md)\n- [dsh-superagent (DeepSeek) vs Devin](https://www.anchorterminal.com/compare/deepseek-superagent-vs-devin.md)\n- [dsh-superagent (DeepSeek) vs Droid CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-droid-cli.md)\n- [dsh-superagent (DeepSeek) vs Pi](https://www.anchorterminal.com/compare/deepseek-superagent-vs-earendil-pi.md)\n- [dsh-superagent (DeepSeek) vs Gemini CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-gemini-cli.md)\n- [dsh-superagent (DeepSeek) vs GitHub Copilot CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-github-copilot-cli.md)\n- [dsh-superagent (DeepSeek) vs goose](https://www.anchorterminal.com/compare/deepseek-superagent-vs-goose.md)\n- [dsh-superagent (DeepSeek) vs Harness²](https://www.anchorterminal.com/compare/deepseek-superagent-vs-harness2.md)\n- [dsh-superagent (DeepSeek) vs HarnessRouter](https://www.anchorterminal.com/compare/deepseek-superagent-vs-harnessrouter.md)\n- [dsh-superagent (DeepSeek) vs Jules](https://www.anchorterminal.com/compare/deepseek-superagent-vs-jules.md)\n- [dsh-superagent (DeepSeek) vs Junie CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-junie.md)\n- [dsh-superagent (DeepSeek) vs Kilo Code CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-kilo-code-cli.md)\n- [dsh-superagent (DeepSeek) vs Kiro CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli.md)\n- [dsh-superagent (DeepSeek) vs mini-swe-agent](https://www.anchorterminal.com/compare/deepseek-superagent-vs-mini-swe-agent.md)\n- [dsh-superagent (DeepSeek) vs MiniMax Code](https://www.anchorterminal.com/compare/deepseek-superagent-vs-minimax-code.md)\n- [dsh-superagent (DeepSeek) vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-mistral-vibe-cli.md)\n- [dsh-superagent (DeepSeek) vs Muse Code](https://www.anchorterminal.com/compare/deepseek-superagent-vs-muse-code.md)\n- [dsh-superagent (DeepSeek) vs OpenAI Codex](https://www.anchorterminal.com/compare/deepseek-superagent-vs-openai-codex.md)\n- [dsh-superagent (DeepSeek) vs OpenCode](https://www.anchorterminal.com/compare/deepseek-superagent-vs-opencode.md)\n- [dsh-superagent (DeepSeek) vs OpenHands](https://www.anchorterminal.com/compare/deepseek-superagent-vs-openhands.md)\n- [dsh-superagent (DeepSeek) vs OpenMausBot](https://www.anchorterminal.com/compare/deepseek-superagent-vs-openmausbot.md)\n- [dsh-superagent (DeepSeek) vs Prime Agent](https://www.anchorterminal.com/compare/deepseek-superagent-vs-prime-agent.md)\n- [dsh-superagent (DeepSeek) vs Qoder CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-qoder-cli.md)\n- [dsh-superagent (DeepSeek) vs Qwen Code](https://www.anchorterminal.com/compare/deepseek-superagent-vs-qwen-code.md)\n- [dsh-superagent (DeepSeek) vs Mirror CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-reflection-mirror.md)\n- [dsh-superagent (DeepSeek) vs Rovo Dev CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-rovo-dev-cli.md)\n- [dsh-superagent (DeepSeek) vs Unstoppable](https://www.anchorterminal.com/compare/deepseek-superagent-vs-unstoppable.md)\n- [dsh-superagent (DeepSeek) vs Vibe-Trading](https://www.anchorterminal.com/compare/deepseek-superagent-vs-vibe-trading.md)\n- [dsh-superagent (DeepSeek) vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/deepseek-superagent-vs-warp.md)\n- [Devin vs Kimi Code CLI](https://www.anchorterminal.com/compare/devin-vs-kimi-code-cli.md)\n- [Droid CLI vs Kimi Code CLI](https://www.anchorterminal.com/compare/droid-cli-vs-kimi-code-cli.md)\n- [Pi vs Kimi Code CLI](https://www.anchorterminal.com/compare/earendil-pi-vs-kimi-code-cli.md)\n- [Gemini CLI vs Kimi Code CLI](https://www.anchorterminal.com/compare/gemini-cli-vs-kimi-code-cli.md)\n- [GitHub Copilot CLI vs Kimi Code CLI](https://www.anchorterminal.com/compare/github-copilot-cli-vs-kimi-code-cli.md)\n- [goose vs Kimi Code CLI](https://www.anchorterminal.com/compare/goose-vs-kimi-code-cli.md)\n- [Harness² vs Kimi Code CLI](https://www.anchorterminal.com/compare/harness2-vs-kimi-code-cli.md)\n- [HarnessRouter vs Kimi Code CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-kimi-code-cli.md)\n- [Jules vs Kimi Code CLI](https://www.anchorterminal.com/compare/jules-vs-kimi-code-cli.md)\n- [Junie CLI vs Kimi Code CLI](https://www.anchorterminal.com/compare/junie-vs-kimi-code-cli.md)\n- [Kilo Code CLI vs Kimi Code CLI](https://www.anchorterminal.com/compare/kilo-code-cli-vs-kimi-code-cli.md)\n- [Kimi Code CLI vs Kiro CLI](https://www.anchorterminal.com/compare/kimi-code-cli-vs-kiro-cli.md)\n- [Kimi Code CLI vs mini-swe-agent](https://www.anchorterminal.com/compare/kimi-code-cli-vs-mini-swe-agent.md)\n- [Kimi Code CLI vs MiniMax Code](https://www.anchorterminal.com/compare/kimi-code-cli-vs-minimax-code.md)\n- [Kimi Code CLI vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/kimi-code-cli-vs-mistral-vibe-cli.md)\n- [Kimi Code CLI vs Muse Code](https://www.anchorterminal.com/compare/kimi-code-cli-vs-muse-code.md)\n- [Kimi Code CLI vs OpenAI Codex](https://www.anchorterminal.com/compare/kimi-code-cli-vs-openai-codex.md)\n- [Kimi Code CLI vs OpenCode](https://www.anchorterminal.com/compare/kimi-code-cli-vs-opencode.md)\n- [Kimi Code CLI vs OpenHands](https://www.anchorterminal.com/compare/kimi-code-cli-vs-openhands.md)\n- [Kimi Code CLI vs OpenMausBot](https://www.anchorterminal.com/compare/kimi-code-cli-vs-openmausbot.md)\n- [Kimi Code CLI vs Prime Agent](https://www.anchorterminal.com/compare/kimi-code-cli-vs-prime-agent.md)\n- [Kimi Code CLI vs Qoder CLI](https://www.anchorterminal.com/compare/kimi-code-cli-vs-qoder-cli.md)\n- [Kimi Code CLI vs Qwen Code](https://www.anchorterminal.com/compare/kimi-code-cli-vs-qwen-code.md)\n- [Kimi Code CLI vs Mirror CLI](https://www.anchorterminal.com/compare/kimi-code-cli-vs-reflection-mirror.md)\n- [Kimi Code CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/kimi-code-cli-vs-rovo-dev-cli.md)\n- [Kimi Code CLI vs Unstoppable](https://www.anchorterminal.com/compare/kimi-code-cli-vs-unstoppable.md)\n- [Kimi Code CLI vs Vibe-Trading](https://www.anchorterminal.com/compare/kimi-code-cli-vs-vibe-trading.md)\n- [Kimi Code CLI vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/kimi-code-cli-vs-warp.md)\n- [Clawboo vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/clawboo-vs-deepseek-superagent.md)\n- [Clawboo vs Kimi Code CLI](https://www.anchorterminal.com/compare/clawboo-vs-kimi-code-cli.md)\n- [CLI Manager vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/cli-manager-vs-deepseek-superagent.md)\n- [CLI Manager vs Kimi Code CLI](https://www.anchorterminal.com/compare/cli-manager-vs-kimi-code-cli.md)\n- [dsh-superagent (DeepSeek) vs Harness](https://www.anchorterminal.com/compare/deepseek-superagent-vs-harness-autonomous.md)\n- [dsh-superagent (DeepSeek) vs Paperclip](https://www.anchorterminal.com/compare/deepseek-superagent-vs-paperclip.md)\n- [dsh-superagent (DeepSeek) vs Parallax](https://www.anchorterminal.com/compare/deepseek-superagent-vs-parallax-agents.md)\n- [Harness vs Kimi Code CLI](https://www.anchorterminal.com/compare/harness-autonomous-vs-kimi-code-cli.md)\n- [Kimi Code CLI vs Paperclip](https://www.anchorterminal.com/compare/kimi-code-cli-vs-paperclip.md)\n- [Kimi Code CLI vs Parallax](https://www.anchorterminal.com/compare/kimi-code-cli-vs-parallax-agents.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-01", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "dsh-superagent (DeepSeek) vs Kimi Code CLI", "url": "" } ], "description": "Kimi Code CLI scores 62.1 (B) to dsh-superagent's 42.1 (E) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "dsh-superagent (DeepSeek) E 42.1", "Kimi Code CLI B 62.1", "scores" ], "h1": "dsh-superagent (DeepSeek) vs Kimi Code CLI", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/deepseek-superagent-vs-kimi-code-cli", "published": "2026-10-01", "section": "tools", "title": "dsh-superagent vs Kimi Code CLI for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kimi-code-cli" }, "tokens": { "markdown": 7100, "slim": 3430 }, "version": 1 }