{ "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": "Kiro CLI scores 60.8 (C) on agent readiness against dsh-superagent (DeepSeek)'s 42.1 (E), and leads in 5 of 7 scored categories.", "b": { "slug": "kiro-cli", "name": "Kiro CLI", "vendor": "Amazon Web Services", "vendorUrl": "https://kiro.dev/cli/", "kind": "harness", "category": "agent-harnesses", "summary": "AWS's coding agent for the terminal and the successor to the Amazon Q Developer CLI. It runs interactive chat, non-interactive runs for pipelines with an API key, MCP servers and an Agent Client Protocol server for editors.", "url": "https://www.anchorterminal.com/tools/kiro-cli", "markdownUrl": "https://www.anchorterminal.com/tools/kiro-cli.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/kiro-cli.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/kiro-cli.json", "dns": "kiro-cli.grade.anchorterminal.com", "repo": "https://github.com/kirodotdev/Kiro", "license": "Proprietary. Licensed as AWS Content under the AWS Customer Agreement and the AWS Intellectual Property Licence (https://kiro.dev/license/). The GitHub repository is the public issue tracker and doesn't hold the source", "transports": [], "packages": [], "auth": "mixed", "authNotes": "`kiro-cli login` with GitHub, Google, AWS Builder ID, AWS IAM Identity Centre or an external identity provider, in a browser or by device flow on a remote machine. Pipelines use an API key in `KIRO_API_KEY`, created at app.kiro.dev by Pro, Pro+, Pro Max and Power subscribers. Keys are long-lived, named and revocable, with no scopes, and API key generation is off by default for subscriptions an administrator manages. An active browser session takes precedence over the key.", "pricing": "freemium", "pricingNotes": "Kiro Free is $0 with 50 credits a month and a reduced model list. Pro is $20 a user a month with 1,000 credits, Pro+ $40 with 2,000, Pro Max $100 with 5,000 and Power $200 with 10,000, and extra credits cost $0.04 each. Models use credits at different rates (Auto is the 1.0x baseline). API keys for headless runs need a paid plan, and a paid plan needs a card. GovCloud prices are about 20 per cent higher with no free tier (checked 2026-10-08).", "priceSummary": "$20 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the pricing page or the CLI changelog (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 4356, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://kiro.dev/docs/cli/", "llmsTxt": "https://kiro.dev/llms.txt", "capabilities": [ "agent.harness", "agent.mcp-client", "agent.multi-agent" ], "tags": [ "official", "harness", "coding-agent", "cli", "closed-source", "mcp", "acp", "llms-txt", "free-tier", "no-card", "telemetry-default-on" ], "lastRelease": "2026-10-14", "graded": true, "anchor": { "graded": true, "score": 60.8, "grade": "C", "agentReady": false, "rank": 581, "ranked": true, "rankOf": 1251, "categoryRank": 17, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 67, "maintenance": 73, "payments": 40, "reliability": 57, "schema": 79, "security": 69, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-17" }, "negative": -4, "negativeNotes": [ "2026-08-04. CVE-2026-18656 and CVE-2026-18657 (bulletin 2026-074-AWS), an uncontrolled search path on Windows let a planted executable in a crafted project directory run when a user opened it. Kiro CLI for Windows before 2.10.0 and Kiro IDE 1.0.0 to 1.0.212. Fixed and published with credit to the reporters, inside six months (https://aws.amazon.com/security/security-bulletins/2026-074-aws/). -2", "2026-05-22. CVE-2026-9255 (bulletin 2026-035-AWS), content piped to kiro-cli on stdin could answer the tool approval prompt, so a local actor could run tools and shell commands without the user's approval. kiro-cli before 1.28.0. Fixed and published, inside six months (https://aws.amazon.com/security/security-bulletins/2026-035-aws/). -2" ], "verdict": "Permission rules follow deny over ask over allow, cloned repositories can't add rules, and a headless session treats every ask as a deny. Content from Free and individual paid accounts is used for service improvement, including model training, unless the user opts out, and API keys for pipelines need a paid plan.", "bestFor": "Teams on AWS that want one agent configuration across terminal, IDE and web, with central permission policy, prompt logging to their own S3 bucket and IAM Identity Centre sign-in.", "strengths": [ "Capability permissions with deny over ask over allow, stored outside the repository so a clone can't add rules", "An untrusted workspace doesn't load its own agents, steering files, MCP configuration or skills, and asks before every shell command", "Headless runs with `--no-interactive`, JSON Lines output, and exit codes 3 and 4 for MCP startup and missing-agent failures", "Twelve minor releases between 26 August and 13 October 2026 in a dated changelog", "Plan prices, the $0.04 credit price and per-model credit multipliers are public, with a free tier of 50 credits a month" ], "weaknesses": [ "Free and individual paid accounts have content used for service improvement, including model training, unless they opt out", "Closed source since it replaced the Apache 2.0 Amazon Q Developer CLI, with no public CI or test suite", "API keys for headless runs need a paid plan, are long-lived and carry no scopes", "The local command sandbox exists only in the V3 engine and is off unless chosen, and AWS says managed permission policies are client-enforced", "Two CVEs in 2026 (CVE-2026-9255 in May, CVE-2026-18656 and CVE-2026-18657 in August), both fixed" ], "agentNotes": [ "Set `KIRO_API_KEY` and pass `--no-interactive` with `--trust-tools=\u003clist\u003e` in pipelines. Keep `--trust-all-tools` for disposable environments", "Pass `--require-mcp-startup` when a run depends on MCP tools. Without it a failed server is logged and the run continues", "Pass `--no-interactive` whenever input is piped from a source you don't control, and run 2.10.0 or later on Windows", "Run `kiro-cli settings telemetry.enabled false` and turn off content collection on Free and individual plans. Both are on by default", "Pick another model if a session names Claude Sonnet 4, which reached end of life in Kiro on 14 October 2026. Kiro doesn't switch it for you" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 4, "avgRating": 2.8, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.8 } ], "editorialScores": { "ergonomics": 67, "maintenance": 73, "payments": 40, "reliability": 57, "schema": 79, "security": 69, "transparency": 66 }, "provenanceScore": 76, "checked": { "categories": { "ergonomics": "2026-10-17", "maintenance": "2026-10-17", "payments": "2026-10-17", "reliability": "2026-10-17", "schema": "2026-10-17", "security": "2026-10-17", "transparency": "2026-10-17" }, "last": "2026-10-17", "lastMoved": "2026-10-28", "oldest": "2026-10-17", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "curl -fsSL https://cli.kiro.dev/install | bash", "headless": { "run": "KIRO_API_KEY=ksk_... kiro-cli chat --no-interactive --trust-tools=read,grep \"Find all TODO comments in src/\"" } }, "letme": { "capability": "https://letme.dev/agent.harness", "tool": "https://letme.dev/kiro-cli" }, "area": "frameworks", "unitPrices": [ { "item": "Kiro Pro", "unit": "month", "usd": 20, "note": "per user, with 1,000 credits" }, { "item": "Add-on credit", "unit": "credit", "usd": 0.04, "note": "paid plans, beyond the plan's credits" } ], "provenance": { "legalEntity": "Amazon Web Services, Inc.", "domain": "kiro.dev", "domainRegistered": "2019-03-01", "endpointOnVendorDomain": null, "terms": "https://aws.amazon.com/agreement/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "", "changelog": "https://kiro.dev/changelog/cli/", "securityTxt": "none", "checked": "2026-10-17", "notes": [ "Kiro's licence page says the Kiro IDE and CLI are licensed as AWS Content under the AWS Customer Agreement and the AWS Intellectual Property Licence. Section 50.14 of the AWS Service Terms names Amazon Web Services, Inc. as the contracting party for subscriptions bought through the Stripe portal.", "The AWS Customer Agreement (last updated 14 August 2026) governs use, with the AWS Service Terms sections 50.3 and 50.14 for Kiro. The AWS Privacy Notice (last updated 18 May 2026) is the privacy link in Kiro's footer.", "kiro.dev/.well-known/security.txt answered 404 on 17 October. aws.amazon.com publishes a security.txt that is valid again, with Expires 2027-10-16 and a Policy of https://vdp.aws.security/.", "No status page for Kiro was found on kiro.dev or in its docs.", "RDAP (Google Registry) gives kiro.dev a registration date of 1 March 2019, before the product." ], "score": 76 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/kiro-cli.json", "live": { "slug": "kiro-cli", "githubStars": 4421, "securityTxt": { "url": "https://kiro.dev/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-31T15:41:47.111941634Z" }, "llmsTxt": { "url": "https://kiro.dev/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-10-31T15:11:03.706002858Z" }, "domain": { "domain": "kiro.dev", "registered": "2019-03-01", "source": "https://pubapi.registry.google/rdap/domain/kiro.dev", "checkedAt": "2026-10-25T13:53:30.938182416Z" }, "pages": [ { "url": "https://kiro.dev/changelog/cli/", "kind": "deprecations", "status": 200, "checkedAt": "2026-10-31T06:14:25.251371933Z", "changedAt": "2026-10-31T06:14:25.251371933Z", "fingerprint": "a590c4863382" }, { "url": "https://kiro.dev/changelog/models/", "kind": "deprecations", "status": 200, "checkedAt": "2026-10-31T06:14:27.388041825Z", "changedAt": "2026-10-31T06:14:27.388041825Z", "fingerprint": "adb4df2f8d03" } ], "github": { "repo": "kirodotdev/kiro", "checkedAt": "2026-10-26T07:37:58.454527374Z", "stars": 4398, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-18T11:35:32Z", "openIssues": 1595, "openPRs": 7, "issuesOpened90d": 1610, "issuesClosed90d": 2659, "prsMerged90d": 2, "ci": { "branch": "main", "runs": 1, "success": 0, "failure": 1, "other": 0, "latest": "failure", "latestAt": "2026-03-23T17:52:28Z" } }, "updatedAt": "2026-10-31T16:02:20.034719841Z" } }, "edges": [ { "by": 42, "category": "reliability", "leads": "kiro-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, the same as the other closed-source harnesses. An install script that verifies SHA-256 checksums, a .deb, an AppImage and a PowerShell script, with macOS, Windows 11 and Linux (glibc 2.34 or newer, or musl) stated (20). No public CI or test suite, since the source isn't published and the GitHub repository is an issue tracker (0). Per the 8 October check, not re-read on 17 October, 1,401 open issues in the shared Kiro tracker, 428 labelled cli, with 96 cli issues opened and 69 closed in the 30 days to 8 October, area labels, a triage label and stale-issue automation. Open reports from the week to 8 October included a `--no-interactive` run that never exits after a refusal (12). A dated changelog for every release and a breaking-change table with a migration guide for V3, which runs beside 2.x until the user opts in, though 2.24.0 stopped loading project `.env` files in a minor version (10). 2.31.1 is the released line, with V3 still an early release that 2.30.0 says becomes the default with CLI 3.0 at the end of October (15). 20+0+12+10+15 = 57." }, "scores": { "a": 15, "b": 57 } }, { "by": 39, "category": "maintenance", "leads": "kiro-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.31.1 on 14 October 2026 (30). At least 12 minor versions (2.20.0 on 26 August to 2.31.0 on 13 October) and their patches (20). A public issue tracker with area labels and triage automation, 69 cli issues closed against 96 opened in the 30 days to 8 October, and a Discord server, per the 8 October check, not re-read on 17 October. We didn't establish how many replies come from staff (14). No SDK and no registry entry. The ACP server is kept current, with a migration guide for clients moving to V3 (6). Closed source, so no CI or dependency health to read. The installer verifies checksums (3). 30+20+14+6+3 = 73." }, "scores": { "a": 34, "b": 73 } }, { "by": 36, "category": "security", "leads": "kiro-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": "Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Telemetry and content collection are on by default for Free and individual accounts, each with a documented opt-out, and enterprise users are opted out. API keys are long-lived and revocable with no scopes, and administrators must switch key generation on (14). Deny over ask over allow across six scopes, hard-coded denies on Kiro's own settings paths, workspace trust and a managed policy that fails closed. Since 2.31.0 (13 October 2026) every V3 user can run `/sandbox` to put agent shell commands and local stdio MCP servers in an operating-system sandbox, with outbound network blocked, limited or open, and `/autonomous on` turns it on first. It is off unless chosen, it doesn't cover the agent, built-in file tools or remote MCP servers, V3 is still an early release beside 2.x, and AWS says managed policies are client-enforced and can be circumvented (17). An untrusted workspace doesn't load its agents, steering, MCP configuration or skills, and can read but not write memories. Compound shell commands are split before matching, and the MCP page warns that servers run outside any sandbox (11). Enterprise prompt logging to the customer's S3 bucket covers the CLI, with daily activity reports and OpenTelemetry export, and individuals have local logs only (11). AWS vulnerability reporting through a HackerOne disclosure programme with no paid bounty, CVEs published in security bulletins with credit to reporters, ISO/IEC 27001:2022 scope and HIPAA eligibility. The aws.amazon.com security.txt is valid again (Expires 2027-10-16), which is the 17 October reading for every AWS listing, and kiro.dev/.well-known/security.txt still answers 404, so 2 are held back for that and 2 for no bounty (16). 14+17+11+11+16 = 69." }, "scores": { "a": 33, "b": 69 } }, { "by": 19, "category": "transparency", "leads": "kiro-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": "Proprietary, with clear terms. The licence page puts the CLI under the AWS Customer Agreement and the AWS Intellectual Property Licence, where the Amazon Q Developer CLI it replaced was Apache 2.0 (15). The data protection page says what is stored for Free, individual and enterprise users, names US East (N. Virginia) for storage, lists inference regions, and gives 60 days for Free Tier abuse detection and 30 days for some models. It agrees with sections 50.3 and 50.14 of the AWS Service Terms. No general retention period for stored content was found, per the 8 October check (22). The models page has a model lifecycle section (page updated 17 October 2026) with Experimental, Active and EOL stages, says Kiro generally schedules model end of life alongside Amazon Bedrock and shows the date in the model picker, and lists Claude Sonnet 4.0 as ending on 14 October 2026. 2.30.0 says V3 becomes the default with CLI 3.0 at the end of October, Classic sessions carry a deprecation notice, and V3 has a breaking-change table and migration guides. No minimum notice period is stated, and we found no notice of the Sonnet 4 date before the 14 October changelog entry (14). Telemetry types are listed and `telemetry.enabled` turns them off, with collection on by default (15). 15+22+14+15 = 66." }, "scores": { "a": 52, "b": 71 } }, { "by": 18, "category": "schema", "leads": "kiro-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. A command reference, a settings reference, an exit-code page and a documented rule format for permissions, plus the Agent Client Protocol methods the CLI implements. No published schema for the stream-json events was found (14). kiro.dev/llms.txt indexes every docs page and each has a Markdown twin, though robots.txt disallows both for crawlers (10). The permissions page states the defaults, what each preset allows and when to pick it, and that headless runs treat ask as deny (16). Rules are validated, an unknown preset rejects the session request, and a malformed managed policy fails closed (12). CI examples, exit codes 0, 1, 3 and 4 and hook exit codes are documented, but code 1 covers every other failure (12). Versioned releases with a dated changelog and a 2.x reference kept beside V3 (15)." }, "scores": { "a": 61, "b": 79 } } ], "facts": [ { "a": "Agent harness", "b": "Agent harness", "name": "Kind" }, { "a": "DeepSeek", "b": "Amazon Web Services", "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": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "Proprietary. Licensed as AWS Content under the AWS Customer Agreement and the AWS Intellectual Property Licence (https://kiro.dev/license/). The GitHub repository is the public issue tracker and doesn't hold the source", "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-14", "name": "Terms last updated" }, { "a": "2026-09-20", "b": "2026-05-18", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "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": "4.4k stars", "name": "Popularity" }, { "a": "none", "b": "2.8/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Kiro CLI scores 60.8 (C) on agent readiness against dsh-superagent (DeepSeek)'s 42.1 (E), and leads in 5 of 7 scored categories.", "question": "Which is better for AI agents, dsh-superagent (DeepSeek) or Kiro CLI?" }, { "answer": "dsh-superagent (DeepSeek) is open source (MIT). No open-source release is listed for Kiro CLI.", "question": "Are dsh-superagent (DeepSeek) and Kiro CLI open source?" } ], "goodFor": [ { "aheadOn": null, "also": [ "Open source", "No incidents deducted, where Kiro 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, 57 against 15", "Schema \u0026 documentation, 79 against 61", "Security \u0026 auth, 69 against 33", "Maintenance \u0026 community, 73 against 34", "Transparency \u0026 trust, 71 against 52" ], "also": null, "goodFor": "Teams on AWS that want one agent configuration across terminal, IDE and web, with central permission policy, prompt logging to their own S3 bucket and IAM Identity Centre sign-in.", "slug": "kiro-cli", "watchFor": "Free and individual paid accounts have content used for service improvement, including model training, unless they opt out" } ], "history": { "deepseek-superagent": null, "kiro-cli": [ { "causes": [ "evidence" ], "date": "2026-10-28", "delta": 0.1, "from": 60.7, "fromGrade": "C", "to": 60.8, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 60.6, "fromGrade": "C", "to": 60.7, "toGrade": "C" }, { "causes": [ "security", "product" ], "date": "2026-10-17", "delta": 0.7, "from": 59.9, "fromGrade": "C", "to": 60.6, "toGrade": "C" } ] }, "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-kiro-cli.json", "title": "Agent Zero vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-kiro-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-kiro-cli.json", "title": "Aider vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/aider-vs-kiro-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-kiro-cli.json", "title": "Amp vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/amp-vs-kiro-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-kiro-cli.json", "title": "Antigravity CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-kiro-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-kiro-cli.json", "title": "Auggie CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/auggie-vs-kiro-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-kiro-cli.json", "title": "Claude Code vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/claude-code-vs-kiro-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-kiro-cli.json", "title": "Cline vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/cline-vs-kiro-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-kiro-cli.json", "title": "Crush vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/crush-vs-kiro-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-kiro-cli.json", "title": "Cursor CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/cursor-cli-vs-kiro-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-kiro-cli.json", "title": "DeepSeek Harness (dsh) vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/deepseek-harness-vs-kiro-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-kimi-code-cli.json", "title": "dsh-superagent (DeepSeek) vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kimi-code-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-kiro-cli.json", "title": "Devin vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/devin-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/droid-cli-vs-kiro-cli.json", "title": "Droid CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/droid-cli-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/earendil-pi-vs-kiro-cli.json", "title": "Pi vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/earendil-pi-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/gemini-cli-vs-kiro-cli.json", "title": "Gemini CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/gemini-cli-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-kiro-cli.json", "title": "GitHub Copilot CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/goose-vs-kiro-cli.json", "title": "goose vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/goose-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/harness2-vs-kiro-cli.json", "title": "Harness² vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/harness2-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/harnessrouter-vs-kiro-cli.json", "title": "HarnessRouter vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/jules-vs-kiro-cli.json", "title": "Jules vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/jules-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/junie-vs-kiro-cli.json", "title": "Junie CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/junie-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-kiro-cli.json", "title": "Kilo Code CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-kiro-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/kiro-cli-vs-mini-swe-agent.json", "title": "Kiro CLI vs mini-swe-agent", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-mini-swe-agent" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-minimax-code.json", "title": "Kiro CLI vs MiniMax Code", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-minimax-code" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-mistral-vibe-cli.json", "title": "Kiro CLI vs Mistral Vibe CLI", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-mistral-vibe-cli" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-muse-code.json", "title": "Kiro CLI vs Muse Code", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-muse-code" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-codex.json", "title": "Kiro CLI vs OpenAI Codex", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-codex" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-opencode.json", "title": "Kiro CLI vs OpenCode", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-opencode" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-openhands.json", "title": "Kiro CLI vs OpenHands", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openhands" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-openmausbot.json", "title": "Kiro CLI vs OpenMausBot", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openmausbot" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-prime-agent.json", "title": "Kiro CLI vs Prime Agent", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-prime-agent" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-qoder-cli.json", "title": "Kiro CLI vs Qoder CLI", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-qoder-cli" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-qwen-code.json", "title": "Kiro CLI vs Qwen Code", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-qwen-code" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-reflection-mirror.json", "title": "Kiro CLI vs Mirror CLI", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-reflection-mirror" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli.json", "title": "Kiro CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-unstoppable.json", "title": "Kiro CLI vs Unstoppable", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-unstoppable" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-vibe-trading.json", "title": "Kiro CLI vs Vibe-Trading", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-vibe-trading" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-warp.json", "title": "Kiro CLI vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/kiro-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-kiro-cli.json", "title": "Clawboo vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/clawboo-vs-kiro-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-kiro-cli.json", "title": "CLI Manager vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/cli-manager-vs-kiro-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-kiro-cli.json", "title": "Harness vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/harness-autonomous-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-paperclip.json", "title": "Kiro CLI vs Paperclip", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-paperclip" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-parallax-agents.json", "title": "Kiro CLI vs Parallax", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-parallax-agents" } ], "panel": null, "scores": [ { "by": 42, "deepseek-superagent": 15, "edge": "kiro-cli", "key": "reliability", "kiro-cli": 57, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 18, "deepseek-superagent": 61, "edge": "kiro-cli", "key": "schema", "kiro-cli": 79, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 0, "deepseek-superagent": 67, "edge": "", "key": "ergonomics", "kiro-cli": 67, "name": "Agent ergonomics", "weight": 13 }, { "by": 36, "deepseek-superagent": 33, "edge": "kiro-cli", "key": "security", "kiro-cli": 69, "name": "Security \u0026 auth", "weight": 14 }, { "by": 0, "deepseek-superagent": 40, "edge": "", "key": "payments", "kiro-cli": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 39, "deepseek-superagent": 34, "edge": "kiro-cli", "key": "maintenance", "kiro-cli": 73, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 19, "deepseek-superagent": 52, "edge": "kiro-cli", "key": "transparency", "kiro-cli": 71, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Kiro CLI scores 60.8 (C) on agent readiness against dsh-superagent (DeepSeek)'s 42.1 (E), and leads in 5 of 7 scored categories. 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.", "kiro-cli": "Permission rules follow deny over ask over allow, cloned repositories can't add rules, and a headless session treats every ask as a deny. Content from Free and individual paid accounts is used for service improvement, including model training, unless the user opts out, and API keys for pipelines need a paid plan." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli", "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli.min.md" }, "markdown": "Kiro CLI scores 60.8 (C) on agent readiness against dsh-superagent (DeepSeek)'s 42.1 (E), and leads in 5 of 7 scored categories. 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- Kiro CLI: grade C, 60.8/100, rank #581 of 1251. Markdown https://www.anchorterminal.com/tools/kiro-cli.md · JSON https://www.anchorterminal.com/api/v1/tools/kiro-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- Open source\n- No incidents deducted, where Kiro 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### Kiro CLI (C)\n\nGood for: Teams on AWS that want one agent configuration across terminal, IDE and web, with central permission policy, prompt logging to their own S3 bucket and IAM Identity Centre sign-in.\n\nAhead on:\n- Reliability, 57 against 15\n- Schema \u0026 documentation, 79 against 61\n- Security \u0026 auth, 69 against 33\n- Maintenance \u0026 community, 73 against 34\n- Transparency \u0026 trust, 71 against 52\n\nWatch for: Free and individual paid accounts have content used for service improvement, including model training, unless they opt out\n\n\n## Why the edge\n\n### Reliability: Kiro CLI +42\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- Kiro CLI (57): Local-package reading, the same as the other closed-source harnesses. An install script that verifies SHA-256 checksums, a .deb, an AppImage and a PowerShell script, with macOS, Windows 11 and Linux (glibc 2.34 or newer, or musl) stated (20). No public CI or test suite, since the source isn't published and the GitHub repository is an issue tracker (0). Per the 8 October check, not re-read on 17 October, 1,401 open issues in the shared Kiro tracker, 428 labelled cli, with 96 cli issues opened and 69 closed in the 30 days to 8 October, area labels, a triage label and stale-issue automation. Open reports from the week to 8 October included a `--no-interactive` run that never exits after a refusal (12). A dated changelog for every release and a breaking-change table with a migration guide for V3, which runs beside 2.x until the user opts in, though 2.24.0 stopped loading project `.env` files in a minor version (10). 2.31.1 is the released line, with V3 still an early release that 2.30.0 says becomes the default with CLI 3.0 at the end of October (15). 20+0+12+10+15 = 57.\n\n### Maintenance \u0026 community: Kiro CLI +39\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- Kiro CLI (73): 2.31.1 on 14 October 2026 (30). At least 12 minor versions (2.20.0 on 26 August to 2.31.0 on 13 October) and their patches (20). A public issue tracker with area labels and triage automation, 69 cli issues closed against 96 opened in the 30 days to 8 October, and a Discord server, per the 8 October check, not re-read on 17 October. We didn't establish how many replies come from staff (14). No SDK and no registry entry. The ACP server is kept current, with a migration guide for clients moving to V3 (6). Closed source, so no CI or dependency health to read. The installer verifies checksums (3). 30+20+14+6+3 = 73.\n\n### Security \u0026 auth: Kiro CLI +36\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- Kiro CLI (69): Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Telemetry and content collection are on by default for Free and individual accounts, each with a documented opt-out, and enterprise users are opted out. API keys are long-lived and revocable with no scopes, and administrators must switch key generation on (14). Deny over ask over allow across six scopes, hard-coded denies on Kiro's own settings paths, workspace trust and a managed policy that fails closed. Since 2.31.0 (13 October 2026) every V3 user can run `/sandbox` to put agent shell commands and local stdio MCP servers in an operating-system sandbox, with outbound network blocked, limited or open, and `/autonomous on` turns it on first. It is off unless chosen, it doesn't cover the agent, built-in file tools or remote MCP servers, V3 is still an early release beside 2.x, and AWS says managed policies are client-enforced and can be circumvented (17). An untrusted workspace doesn't load its agents, steering, MCP configuration or skills, and can read but not write memories. Compound shell commands are split before matching, and the MCP page warns that servers run outside any sandbox (11). Enterprise prompt logging to the customer's S3 bucket covers the CLI, with daily activity reports and OpenTelemetry export, and individuals have local logs only (11). AWS vulnerability reporting through a HackerOne disclosure programme with no paid bounty, CVEs published in security bulletins with credit to reporters, ISO/IEC 27001:2022 scope and HIPAA eligibility. The aws.amazon.com security.txt is valid again (Expires 2027-10-16), which is the 17 October reading for every AWS listing, and kiro.dev/.well-known/security.txt still answers 404, so 2 are held back for that and 2 for no bounty (16). 14+17+11+11+16 = 69.\n\n### Transparency \u0026 trust: Kiro CLI +19\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- Kiro CLI (71): Proprietary, with clear terms. The licence page puts the CLI under the AWS Customer Agreement and the AWS Intellectual Property Licence, where the Amazon Q Developer CLI it replaced was Apache 2.0 (15). The data protection page says what is stored for Free, individual and enterprise users, names US East (N. Virginia) for storage, lists inference regions, and gives 60 days for Free Tier abuse detection and 30 days for some models. It agrees with sections 50.3 and 50.14 of the AWS Service Terms. No general retention period for stored content was found, per the 8 October check (22). The models page has a model lifecycle section (page updated 17 October 2026) with Experimental, Active and EOL stages, says Kiro generally schedules model end of life alongside Amazon Bedrock and shows the date in the model picker, and lists Claude Sonnet 4.0 as ending on 14 October 2026. 2.30.0 says V3 becomes the default with CLI 3.0 at the end of October, Classic sessions carry a deprecation notice, and V3 has a breaking-change table and migration guides. No minimum notice period is stated, and we found no notice of the Sonnet 4 date before the 14 October changelog entry (14). Telemetry types are listed and `telemetry.enabled` turns them off, with collection on by default (15). 15+22+14+15 = 66.\n\n### Schema \u0026 documentation: Kiro CLI +18\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- Kiro CLI (79): Framework reading. A command reference, a settings reference, an exit-code page and a documented rule format for permissions, plus the Agent Client Protocol methods the CLI implements. No published schema for the stream-json events was found (14). kiro.dev/llms.txt indexes every docs page and each has a Markdown twin, though robots.txt disallows both for crawlers (10). The permissions page states the defaults, what each preset allows and when to pick it, and that headless runs treat ask as deny (16). Rules are validated, an unknown preset rejects the session request, and a malformed managed policy fails closed (12). CI examples, exit codes 0, 1, 3 and 4 and hook exit codes are documented, but code 1 covers every other failure (12). Versioned releases with a dated changelog and a 2.x reference kept beside V3 (15).\n\n## Score by category\n\n| Category | Weight | dsh-superagent (DeepSeek) | Kiro CLI | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 15 | 57 | Kiro CLI +42 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 61 | 79 | Kiro CLI +18 |\n| Agent ergonomics | 13% (16.2 this run) | 67 | 67 | even |\n| Security \u0026 auth | 14% (17.5 this run) | 33 | 69 | Kiro CLI +36 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 40 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 34 | 73 | Kiro CLI +39 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 52 | 71 | Kiro CLI +19 |\n| Negative events | ≤15 | 0 | -4 | |\n| **Total** | | **42.1 · E** | **60.8 · C** | |\n\n## Facts side by side\n\n| Fact | dsh-superagent (DeepSeek) | Kiro CLI |\n| --- | --- | --- |\n| Kind | Agent harness | Agent harness |\n| Vendor | DeepSeek | Amazon Web Services |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | Token | OAuth or key |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| Licence | MIT | Proprietary. Licensed as AWS Content under the AWS Customer Agreement and the AWS Intellectual Property Licence (https://kiro.dev/license/). The GitHub repository is the public issue tracker and doesn't hold the source |\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-14 |\n| Privacy policy last updated | 2026-09-20 | 2026-05-18 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\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 | 4.4k stars |\n| Agent reviews | none | 2.8/5 (4) |\n\n## How the scores have moved\n\n### dsh-superagent (DeepSeek)\n\nNo score change since it was listed.\n\n### Kiro CLI\n\n- +0.1 on 28 October 2026: new evidence\n- +0.1 on 27 October 2026: checklist\n- +0.7 on 17 October 2026: security, product\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**Kiro CLI.** Permission rules follow deny over ask over allow, cloned repositories can't add rules, and a headless session treats every ask as a deny. Content from Free and individual paid accounts is used for service improvement, including model training, unless the user opts out, and API keys for pipelines need a paid plan.\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### Kiro CLI\n\n1. Set `KIRO_API_KEY` and pass `--no-interactive` with `--trust-tools=\u003clist\u003e` in pipelines. Keep `--trust-all-tools` for disposable environments\n2. Pass `--require-mcp-startup` when a run depends on MCP tools. Without it a failed server is logged and the run continues\n3. Pass `--no-interactive` whenever input is piped from a source you don't control, and run 2.10.0 or later on Windows\n4. Run `kiro-cli settings telemetry.enabled false` and turn off content collection on Free and individual plans. Both are on by default\n5. Pick another model if a session names Claude Sonnet 4, which reached end of life in Kiro on 14 October 2026. Kiro doesn't switch it for you\n\n## Questions\n\n### Which is better for AI agents, dsh-superagent (DeepSeek) or Kiro CLI?\n\nKiro CLI scores 60.8 (C) on agent readiness against dsh-superagent (DeepSeek)'s 42.1 (E), and leads in 5 of 7 scored categories.\n\n### Are dsh-superagent (DeepSeek) and Kiro CLI open source?\n\ndsh-superagent (DeepSeek) is open source (MIT). No open-source release is listed for Kiro CLI.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli.json, and with the fewest tokens: https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"deepseek-superagent\", \"b\": \"kiro-cli\"}`. From a terminal: `anchor compare deepseek-superagent kiro-cli`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/deepseek-superagent.json and https://www.anchorterminal.com/api/v1/tools/kiro-cli.json\n\n## Other comparisons with dsh-superagent (DeepSeek) or Kiro CLI\n\n- [Agent Zero vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/agent-zero-vs-deepseek-superagent.md)\n- [Agent Zero vs Kiro CLI](https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli.md)\n- [Aider vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/aider-vs-deepseek-superagent.md)\n- [Aider vs Kiro CLI](https://www.anchorterminal.com/compare/aider-vs-kiro-cli.md)\n- [Amp vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/amp-vs-deepseek-superagent.md)\n- [Amp vs Kiro CLI](https://www.anchorterminal.com/compare/amp-vs-kiro-cli.md)\n- [Antigravity CLI vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/antigravity-cli-vs-deepseek-superagent.md)\n- [Antigravity CLI vs Kiro CLI](https://www.anchorterminal.com/compare/antigravity-cli-vs-kiro-cli.md)\n- [Auggie CLI vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/auggie-vs-deepseek-superagent.md)\n- [Auggie CLI vs Kiro CLI](https://www.anchorterminal.com/compare/auggie-vs-kiro-cli.md)\n- [Claude Code vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/claude-code-vs-deepseek-superagent.md)\n- [Claude Code vs Kiro CLI](https://www.anchorterminal.com/compare/claude-code-vs-kiro-cli.md)\n- [Cline vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/cline-vs-deepseek-superagent.md)\n- [Cline vs Kiro CLI](https://www.anchorterminal.com/compare/cline-vs-kiro-cli.md)\n- [Crush vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/crush-vs-deepseek-superagent.md)\n- [Crush vs Kiro CLI](https://www.anchorterminal.com/compare/crush-vs-kiro-cli.md)\n- [Cursor CLI vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/cursor-cli-vs-deepseek-superagent.md)\n- [Cursor CLI vs Kiro CLI](https://www.anchorterminal.com/compare/cursor-cli-vs-kiro-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 Kiro CLI](https://www.anchorterminal.com/compare/deepseek-harness-vs-kiro-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 Kimi Code CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-kimi-code-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 Kiro CLI](https://www.anchorterminal.com/compare/devin-vs-kiro-cli.md)\n- [Droid CLI vs Kiro CLI](https://www.anchorterminal.com/compare/droid-cli-vs-kiro-cli.md)\n- [Pi vs Kiro CLI](https://www.anchorterminal.com/compare/earendil-pi-vs-kiro-cli.md)\n- [Gemini CLI vs Kiro CLI](https://www.anchorterminal.com/compare/gemini-cli-vs-kiro-cli.md)\n- [GitHub Copilot CLI vs Kiro CLI](https://www.anchorterminal.com/compare/github-copilot-cli-vs-kiro-cli.md)\n- [goose vs Kiro CLI](https://www.anchorterminal.com/compare/goose-vs-kiro-cli.md)\n- [Harness² vs Kiro CLI](https://www.anchorterminal.com/compare/harness2-vs-kiro-cli.md)\n- [HarnessRouter vs Kiro CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-kiro-cli.md)\n- [Jules vs Kiro CLI](https://www.anchorterminal.com/compare/jules-vs-kiro-cli.md)\n- [Junie CLI vs Kiro CLI](https://www.anchorterminal.com/compare/junie-vs-kiro-cli.md)\n- [Kilo Code CLI vs Kiro CLI](https://www.anchorterminal.com/compare/kilo-code-cli-vs-kiro-cli.md)\n- [Kimi Code CLI vs Kiro CLI](https://www.anchorterminal.com/compare/kimi-code-cli-vs-kiro-cli.md)\n- [Kiro CLI vs mini-swe-agent](https://www.anchorterminal.com/compare/kiro-cli-vs-mini-swe-agent.md)\n- [Kiro CLI vs MiniMax Code](https://www.anchorterminal.com/compare/kiro-cli-vs-minimax-code.md)\n- [Kiro CLI vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-mistral-vibe-cli.md)\n- [Kiro CLI vs Muse Code](https://www.anchorterminal.com/compare/kiro-cli-vs-muse-code.md)\n- [Kiro CLI vs OpenAI Codex](https://www.anchorterminal.com/compare/kiro-cli-vs-openai-codex.md)\n- [Kiro CLI vs OpenCode](https://www.anchorterminal.com/compare/kiro-cli-vs-opencode.md)\n- [Kiro CLI vs OpenHands](https://www.anchorterminal.com/compare/kiro-cli-vs-openhands.md)\n- [Kiro CLI vs OpenMausBot](https://www.anchorterminal.com/compare/kiro-cli-vs-openmausbot.md)\n- [Kiro CLI vs Prime Agent](https://www.anchorterminal.com/compare/kiro-cli-vs-prime-agent.md)\n- [Kiro CLI vs Qoder CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-qoder-cli.md)\n- [Kiro CLI vs Qwen Code](https://www.anchorterminal.com/compare/kiro-cli-vs-qwen-code.md)\n- [Kiro CLI vs Mirror CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-reflection-mirror.md)\n- [Kiro CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli.md)\n- [Kiro CLI vs Unstoppable](https://www.anchorterminal.com/compare/kiro-cli-vs-unstoppable.md)\n- [Kiro CLI vs Vibe-Trading](https://www.anchorterminal.com/compare/kiro-cli-vs-vibe-trading.md)\n- [Kiro CLI vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/kiro-cli-vs-warp.md)\n- [Clawboo vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/clawboo-vs-deepseek-superagent.md)\n- [Clawboo vs Kiro CLI](https://www.anchorterminal.com/compare/clawboo-vs-kiro-cli.md)\n- [CLI Manager vs dsh-superagent (DeepSeek)](https://www.anchorterminal.com/compare/cli-manager-vs-deepseek-superagent.md)\n- [CLI Manager vs Kiro CLI](https://www.anchorterminal.com/compare/cli-manager-vs-kiro-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 Kiro CLI](https://www.anchorterminal.com/compare/harness-autonomous-vs-kiro-cli.md)\n- [Kiro CLI vs Paperclip](https://www.anchorterminal.com/compare/kiro-cli-vs-paperclip.md)\n- [Kiro CLI vs Parallax](https://www.anchorterminal.com/compare/kiro-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 Kiro CLI", "url": "" } ], "description": "Kiro CLI scores 60.8 (C) 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", "Kiro CLI C 60.8", "scores" ], "h1": "dsh-superagent (DeepSeek) vs Kiro CLI", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/deepseek-superagent-vs-kiro-cli", "published": "2026-10-01", "section": "tools", "title": "dsh-superagent vs Kiro CLI for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-01", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli" }, "tokens": { "markdown": 7050, "slim": 3480 }, "version": 1 }