{ "data": { "a": { "slug": "emdash", "name": "Emdash", "vendor": "General Action, Inc.", "vendorUrl": "https://emdash.sh", "kind": "harness", "category": "agent-harnesses", "summary": "Emdash is an open-source desktop app that runs coding agents such as Claude Code, Codex, OpenCode and Amp in parallel, each in its own Git worktree, locally or on remote machines over SSH, with issue intake and pull requests.", "url": "https://www.anchorterminal.com/tools/emdash", "markdownUrl": "https://www.anchorterminal.com/tools/emdash.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/emdash.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/emdash.json", "dns": "emdash.grade.anchorterminal.com", "repo": "https://github.com/generalaction/emdash", "license": "Apache-2.0", "transports": [], "packages": [], "auth": "none", "pricing": "free", "pricingNotes": "Free and open source. You pay for the coding agents it runs, through your own subscriptions or API keys (checked 2026-11-07).", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No payment protocol in the repository or README (checked 2026-11-07).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-07" }, "docsUrl": "https://emdash.sh/docs", "capabilities": [ "agent.harness", "agent.multi-agent" ], "tags": [ "open-source", "apache-2.0", "desktop-app", "telemetry", "new" ], "lastRelease": "2026-11-06", "graded": true, "anchor": { "graded": true, "score": 53.9, "grade": "D", "agentReady": false, "rank": 927, "ranked": true, "rankOf": 1486, "categoryRank": 35, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 55, "maintenance": 70, "payments": 60, "reliability": 55, "schema": 55, "security": 38, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-07" }, "negative": 0, "verdict": "A mature open-source app for parallel coding agents in Git worktrees, with issue intake from a dozen trackers and remote machines over SSH. Telemetry is on unless you turn it off, and no test workflow was found in the repository.", "bestFor": "Developers who want parallel agents in worktrees, fed from their issue tracker, locally or over SSH.", "strengths": [ "Each task in its own Git worktree and branch", "Issues from Linear, GitHub, Jira, GitLab, Asana and more go straight to an agent", "Works on remote machines over SSH", "Apache 2.0, version 1.2, with macOS, Windows and Linux builds" ], "weaknesses": [ "Telemetry on unless turned off in Settings or with TELEMETRY_ENABLED=false", "No test workflow found, only consistency and release workflows", "No security policy file" ], "agentNotes": [ "Launch with TELEMETRY_ENABLED=false if you don't want telemetry", "Use the SSH mode to keep agents on a remote machine" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.9 } ], "editorialScores": { "ergonomics": 55, "maintenance": 70, "payments": 60, "reliability": 55, "schema": 55, "security": 38, "transparency": 68 }, "provenanceScore": 40, "checked": { "categories": { "ergonomics": "2026-11-07", "maintenance": "2026-11-07", "payments": "2026-11-07", "reliability": "2026-11-07", "schema": "2026-11-07", "security": "2026-11-07", "transparency": "2026-11-07" }, "last": "2026-11-07", "oldest": "2026-11-07", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "brew install --cask emdash" }, "letme": { "capability": "https://letme.dev/agent.harness", "tool": "https://letme.dev/emdash" }, "area": "frameworks", "provenance": { "legalEntity": "General Action, Inc.", "domain": "emdash.sh", "domainRegistered": "", "domainNote": "Not looked up: RDAP isn't requested under the 1 November 2026 rules.", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-07", "notes": [ "The licence names General Action, Inc.. The repository is github.com/generalaction/emdash." ], "score": 40 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/emdash.json", "live": { "slug": "emdash", "securityTxt": { "url": "https://emdash.sh/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:15.230445185Z" }, "updatedAt": "2026-11-07T16:01:15.230445185Z" } }, "answer": "Kiro CLI scores 59.8 (C) on agent readiness against Emdash's 53.9 (D), and leads in 6 of 7 scored categories. Emdash leads on payments \u0026 pricing.", "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-11-03", "graded": true, "anchor": { "graded": true, "score": 59.8, "grade": "C", "agentReady": false, "rank": 675, "ranked": true, "rankOf": 1486, "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-11-03" }, "negative": -5, "negativeNotes": [ "2026-10-23. Released fixes with no advisory, one term. 2.33.0 (20 October 2026) says V3 hook commands on Windows no longer run a same-named program from the working directory and the semantic-search model download no longer extracts a file outside its model directory. 2.34.0 (23 October) says V3 headless mode no longer approves requests that name no trusted tool and remote HTTP MCP servers follow only same-origin redirects. No AWS bulletin or CVE covers them on 3 November (https://kiro.dev/changelog/cli/2-34/). -3", "2026-08-04. CVE-2026-18657 (bulletin 2026-074-AWS, High, CVSS 3.1 7.8), an uncontrolled search path on Windows let a planted executable in a crafted project directory run when a user started Kiro CLI there. Kiro CLI for Windows before 2.10.0. CVE-2026-18656 in the same bulletin is the Kiro IDE record. Fixed and published with credit to the reporter, over two months ago (https://aws.amazon.com/security/security-bulletins/2026-074-aws/). -1", "2026-05-22. CVE-2026-9255 (bulletin 2026-035-AWS, High, CVSS 3.1 7.8), 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, over two months ago (https://aws.amazon.com/security/security-bulletins/2026-035-aws/). -1" ], "verdict": "Permission rules follow deny over ask over allow, and since 3.0.0 (3 November 2026) the V3 engine with workspace trust is the default. Content from Free and individual paid accounts is used for service improvement, including model training, unless the user opts out, and October releases fixed approval and Windows search-path flaws with no security advisory.", "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", "25 dated releases between 11 August and 3 November 2026, with 3.0.0's breaking changes listed in the release", "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 is off unless chosen even with V3 the default, and AWS says managed permission policies are client-enforced", "Two CLI CVEs in 2026, both fixed, and fixes for a Windows search-path flaw and a headless approval flaw in October with no advisory" ], "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", "Run 2.34.0 or later. Earlier V3 headless runs could approve requests naming no trusted tool, and Windows hooks could run a planted program", "Run `kiro-cli settings telemetry.enabled false` and turn off content collection on Free and individual plans. Both are on by default", "Remove `autocomplete`, `inline`, `translate`, `theme` and `dashboard` from scripts, which 3.0.0 retired. Pass `--v2` to keep the V2 agent" ], "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": 59.8 } ], "editorialScores": { "ergonomics": 67, "maintenance": 73, "payments": 40, "reliability": 57, "schema": 79, "security": 69, "transparency": 66 }, "provenanceScore": 76, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "lastMoved": "2026-11-03", "oldest": "2026-11-03", "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-11-03", "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 3 November. aws.amazon.com publishes a valid security.txt, 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": 4451, "securityTxt": { "url": "https://kiro.dev/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:58.530193954Z" }, "llmsTxt": { "url": "https://kiro.dev/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:49.153468899Z" }, "domain": { "domain": "kiro.dev", "registered": "2019-03-01", "source": "https://pubapi.registry.google/rdap/domain/kiro.dev", "checkedAt": "2026-11-01T14:19:40.504330069Z" }, "pages": [ { "url": "https://kiro.dev/changelog/cli/", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:11:59.811836973Z", "changedAt": "2026-11-07T14:11:59.811836973Z", "fingerprint": "7d3768b7d66b" }, { "url": "https://kiro.dev/changelog/cli/3-0/", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:12:02.187245628Z", "changedAt": "2026-11-07T14:12:02.187245628Z", "fingerprint": "2ea0acd7c658" }, { "url": "https://kiro.dev/changelog/models/", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:12:03.994022159Z", "changedAt": "2026-11-07T14:12:03.994022159Z", "fingerprint": "9f060fb426e5" } ], "github": { "repo": "kirodotdev/kiro", "checkedAt": "2026-11-02T08:58:44.34897744Z", "stars": 4431, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-18T11:35:32Z", "openIssues": 1513, "openPRs": 7, "issuesOpened90d": 1572, "issuesClosed90d": 2613, "prsMerged90d": 2, "ci": { "branch": "main", "runs": 1, "success": 0, "failure": 1, "other": 0, "latest": "failure", "latestAt": "2026-03-23T17:52:28Z" }, "replies": { "sampled": 1, "unanswered": 1 } }, "updatedAt": "2026-11-07T16:01:58.530193954Z" } }, "edges": [ { "by": 31, "category": "security", "leads": "kiro-cli", "name": "Security \u0026 auth", "reasons": { "a": "Harness reading. Telemetry is described as optional and disabled in Settings or with TELEMETRY_ENABLED=false, which reads as on by default (15 of 30). Worktree per task and remote machines over SSH (10 of 20). No prompt-injection guidance (5). No audit log (5). No security policy file found (3). 15 + 10 + 5 + 5 + 3 = 38.", "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. V3 is the default since 3.0.0 (3 November 2026), interactive V3 sessions ask before loading a folder's hooks, agents and MCP servers since 2.33.0, and `/sandbox` puts agent shell commands and local stdio MCP servers in an operating-system sandbox. The sandbox is off unless chosen and doesn't cover the agent, built-in file tools or remote MCP servers, 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, 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 (Expires 2027-10-16) and kiro.dev/.well-known/security.txt answers 404, so 2 are held back for that and 2 for no bounty (16). 14+17+11+11+16 = 69." }, "scores": { "a": 38, "b": 69 } }, { "by": 24, "category": "schema", "leads": "kiro-cli", "name": "Schema \u0026 documentation", "reasons": { "a": "Harness reading. Docs site and a workspace server package (55).", "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": 55, "b": 79 } }, { "by": 20, "category": "payments", "leads": "emdash", "name": "Payments \u0026 pricing", "reasons": { "a": "Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60.", "b": "Harness reading of the published rubric, scored on the Kiro subscription the CLI needs. No payment protocol (0). Plan prices, the $0.04 credit price and per-model credit multipliers are public without a login (20). Kiro Free has 50 credits a month, and the pricing page asks for a card only on upgrade (20). A person signs in through a browser or device flow, and the API key for headless runs is created by hand at app.kiro.dev on a paid plan (0)." }, "scores": { "a": 60, "b": 40 } }, { "by": 17, "category": "transparency", "leads": "kiro-cli", "name": "Transparency \u0026 trust", "reasons": { "a": "Apache 2.0 (30). A telemetry page on the docs site (not read) (18 of 30). No deprecation policy (5). Disclosed with an opt-out (15 of 20). 30 + 18 + 5 + 15 = 68.", "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, per the 8 October check (15). The data protection page (updated 23 October 2026) says what is stored for Free, individual and enterprise users, names US East (N. Virginia) for storage, 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, read on 8 October. No general retention period for stored content was found (22). The models page has a model lifecycle section with Experimental, Active and EOL stages and dates, and Claude Sonnet 4 ended on 14 October 2026. 3.0.0 made V3 the default as 2.30.0 announced and retired the Classic interface 34 days after the 2.26.0 deprecation notice, but the desktop app and inline autocomplete were retired in the same release with no earlier notice found, and no minimum notice period is stated (14). Telemetry types are listed and `kiro-cli settings telemetry.enabled` turns them off, with collection on by default. The data protection page's CLI steps still point to the desktop app's Preferences, which 3.0.0 retired (15). 15+22+14+15 = 66." }, "scores": { "a": 54, "b": 71 } }, { "by": 12, "category": "ergonomics", "leads": "kiro-cli", "name": "Agent ergonomics", "reasons": { "a": "Harness reading. Issue intake from Linear, GitHub, Jira and others, diff review, pull requests and CI checks in one place, local or over SSH (55).", "b": "Framework reading, adapted to a harness driven by a pipeline. `--trust-tools` limits approved tools, `disabledTools` removes MCP tools per server, tool search loads MCP tools on demand, and custom agents carry their own tool set (20). Compaction and a workflow timeout (`KIRO_HEADLESS_WORKFLOW_TIMEOUT_SECS`, six hours by default) exist, but no cap on turns or run time for a plain headless run was found (10). Distinct exit codes for MCP startup failure and a missing agent, `--require-mcp-startup`, and a final interruption record in stream-json, with exit 1 for everything else (14). Sessions are saved every turn, with `--resume`, `--resume-id` and checkpoints with rewind (15). No SDK. The programmatic interfaces are the headless command and the ACP server, and a headless run needs a paid-plan API key and explicit trust flags (8)." }, "scores": { "a": 55, "b": 67 } } ], "facts": [ { "a": "Agent harness", "b": "Agent harness", "name": "Kind" }, { "a": "General Action, Inc.", "b": "Amazon Web Services", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "None", "b": "OAuth or key", "name": "Auth" }, { "a": "Free", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Apache-2.0", "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-11-06", "b": "2026-11-03", "name": "Last release" }, { "a": "no document linked", "b": "2026-08-14", "name": "Terms last updated" }, { "a": "no document linked", "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 59.8 (C) on agent readiness against Emdash's 53.9 (D), and leads in 6 of 7 scored categories. Emdash leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Emdash or Kiro CLI?" }, { "answer": "Emdash is open source (Apache-2.0). No open-source release is listed for Kiro CLI.", "question": "Are Emdash and Kiro CLI open source?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 60 against 40" ], "also": [ "No key needed to call it", "Open source", "No incidents deducted, where Kiro CLI loses 5 points for them" ], "goodFor": "Developers who want parallel agents in worktrees, fed from their issue tracker, locally or over SSH.", "slug": "emdash", "watchFor": "Telemetry on unless turned off in Settings or with TELEMETRY_ENABLED=false" }, { "aheadOn": [ "Schema \u0026 documentation, 79 against 55", "Agent ergonomics, 67 against 55", "Security \u0026 auth, 69 against 38", "Transparency \u0026 trust, 71 against 54" ], "also": [ "Free to start without a card" ], "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": { "emdash": null, "kiro-cli": [ { "causes": [ "security" ], "date": "2026-11-03", "delta": -1, "from": 60.8, "fromGrade": "C", "to": 59.8, "toGrade": "C" }, { "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" } ] }, "job": { "capability": "agent.harness", "name": "Agent harnesses" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agent-zero-vs-emdash.json", "title": "Agent Zero vs Emdash", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-emdash" }, { "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-emdash.json", "title": "Aider vs Emdash", "url": "https://www.anchorterminal.com/compare/aider-vs-emdash" }, { "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-emdash.json", "title": "Amp vs Emdash", "url": "https://www.anchorterminal.com/compare/amp-vs-emdash" }, { "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-emdash.json", "title": "Antigravity CLI vs Emdash", "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-emdash" }, { "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-emdash.json", "title": "Auggie CLI vs Emdash", "url": "https://www.anchorterminal.com/compare/auggie-vs-emdash" }, { "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/axlr-vs-emdash.json", "title": "AXLR vs Emdash", "url": "https://www.anchorterminal.com/compare/axlr-vs-emdash" }, { "json": "https://www.anchorterminal.com/compare/axlr-vs-kiro-cli.json", "title": "AXLR vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/axlr-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/claude-code-vs-emdash.json", "title": "Claude Code vs Emdash", "url": "https://www.anchorterminal.com/compare/claude-code-vs-emdash" }, { "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-emdash.json", "title": "Cline vs Emdash", "url": "https://www.anchorterminal.com/compare/cline-vs-emdash" }, { "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/conductor-vs-emdash.json", "title": "Conductor vs Emdash", "url": "https://www.anchorterminal.com/compare/conductor-vs-emdash" }, { "json": "https://www.anchorterminal.com/compare/conductor-vs-kiro-cli.json", "title": "Conductor vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/conductor-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/crush-vs-emdash.json", "title": "Crush vs Emdash", "url": "https://www.anchorterminal.com/compare/crush-vs-emdash" }, { "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-emdash.json", "title": "Cursor CLI vs Emdash", "url": "https://www.anchorterminal.com/compare/cursor-cli-vs-emdash" }, { "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-emdash.json", "title": "DeepSeek Harness (dsh) vs Emdash", "url": "https://www.anchorterminal.com/compare/deepseek-harness-vs-emdash" }, { "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-emdash.json", "title": "dsh-superagent (DeepSeek) vs Emdash", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-emdash" }, { "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/devin-vs-emdash.json", "title": "Devin vs Emdash", "url": "https://www.anchorterminal.com/compare/devin-vs-emdash" }, { "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-emdash.json", "title": "Droid CLI vs Emdash", "url": "https://www.anchorterminal.com/compare/droid-cli-vs-emdash" }, { "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-emdash.json", "title": "Pi vs Emdash", "url": "https://www.anchorterminal.com/compare/earendil-pi-vs-emdash" }, { "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/emdash-vs-gemini-cli.json", "title": "Emdash vs Gemini CLI", "url": "https://www.anchorterminal.com/compare/emdash-vs-gemini-cli" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-github-copilot-cli.json", "title": "Emdash vs GitHub Copilot CLI", "url": "https://www.anchorterminal.com/compare/emdash-vs-github-copilot-cli" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-goose.json", "title": "Emdash vs goose", "url": "https://www.anchorterminal.com/compare/emdash-vs-goose" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-harness2.json", "title": "Emdash vs Harness²", "url": "https://www.anchorterminal.com/compare/emdash-vs-harness2" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-harnessrouter.json", "title": "Emdash vs HarnessRouter", "url": "https://www.anchorterminal.com/compare/emdash-vs-harnessrouter" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-jules.json", "title": "Emdash vs Jules", "url": "https://www.anchorterminal.com/compare/emdash-vs-jules" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-junie.json", "title": "Emdash vs Junie CLI", "url": "https://www.anchorterminal.com/compare/emdash-vs-junie" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-kilo-code-cli.json", "title": "Emdash vs Kilo Code CLI", "url": "https://www.anchorterminal.com/compare/emdash-vs-kilo-code-cli" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-kimi-code-cli.json", "title": "Emdash vs Kimi Code CLI", "url": "https://www.anchorterminal.com/compare/emdash-vs-kimi-code-cli" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-letta.json", "title": "Emdash vs Letta", "url": "https://www.anchorterminal.com/compare/emdash-vs-letta" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-mini-swe-agent.json", "title": "Emdash vs mini-swe-agent", "url": "https://www.anchorterminal.com/compare/emdash-vs-mini-swe-agent" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-minimax-code.json", "title": "Emdash vs MiniMax Code", "url": "https://www.anchorterminal.com/compare/emdash-vs-minimax-code" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-mistral-vibe-cli.json", "title": "Emdash vs Mistral Vibe CLI", "url": "https://www.anchorterminal.com/compare/emdash-vs-mistral-vibe-cli" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-muse-code.json", "title": "Emdash vs Muse Code", "url": "https://www.anchorterminal.com/compare/emdash-vs-muse-code" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-openai-agents-api.json", "title": "Emdash vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/emdash-vs-openai-agents-api" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-openai-codex.json", "title": "Emdash vs OpenAI Codex", "url": "https://www.anchorterminal.com/compare/emdash-vs-openai-codex" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-opencode.json", "title": "Emdash vs OpenCode", "url": "https://www.anchorterminal.com/compare/emdash-vs-opencode" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-openhands.json", "title": "Emdash vs OpenHands", "url": "https://www.anchorterminal.com/compare/emdash-vs-openhands" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-openmausbot.json", "title": "Emdash vs OpenMausBot", "url": "https://www.anchorterminal.com/compare/emdash-vs-openmausbot" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-orca.json", "title": "Emdash vs Orca", "url": "https://www.anchorterminal.com/compare/emdash-vs-orca" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-paseo.json", "title": "Emdash vs Paseo", "url": "https://www.anchorterminal.com/compare/emdash-vs-paseo" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-prime-agent.json", "title": "Emdash vs Prime Agent", "url": "https://www.anchorterminal.com/compare/emdash-vs-prime-agent" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-qoder-cli.json", "title": "Emdash vs Qoder CLI", "url": "https://www.anchorterminal.com/compare/emdash-vs-qoder-cli" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-qwen-code.json", "title": "Emdash vs Qwen Code", "url": "https://www.anchorterminal.com/compare/emdash-vs-qwen-code" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-reflection-mirror.json", "title": "Emdash vs Mirror CLI", "url": "https://www.anchorterminal.com/compare/emdash-vs-reflection-mirror" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-rovo-dev-cli.json", "title": "Emdash vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/emdash-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-sculptor.json", "title": "Emdash vs Sculptor", "url": "https://www.anchorterminal.com/compare/emdash-vs-sculptor" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-t3-code.json", "title": "Emdash vs T3 Code", "url": "https://www.anchorterminal.com/compare/emdash-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-traycer.json", "title": "Emdash vs Traycer", "url": "https://www.anchorterminal.com/compare/emdash-vs-traycer" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-unstoppable.json", "title": "Emdash vs Unstoppable", "url": "https://www.anchorterminal.com/compare/emdash-vs-unstoppable" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-verdent.json", "title": "Emdash vs Verdent", "url": "https://www.anchorterminal.com/compare/emdash-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-vibe-trading.json", "title": "Emdash vs Vibe-Trading", "url": "https://www.anchorterminal.com/compare/emdash-vs-vibe-trading" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-warp.json", "title": "Emdash vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/emdash-vs-warp" }, { "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-letta.json", "title": "Kiro CLI vs Letta", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-letta" }, { "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-agents-api.json", "title": "Kiro CLI vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-agents-api" }, { "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-orca.json", "title": "Kiro CLI vs Orca", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-orca" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-paseo.json", "title": "Kiro CLI vs Paseo", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-paseo" }, { "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-sculptor.json", "title": "Kiro CLI vs Sculptor", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-sculptor" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-t3-code.json", "title": "Kiro CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-traycer.json", "title": "Kiro CLI vs Traycer", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-traycer" }, { "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-verdent.json", "title": "Kiro CLI vs Verdent", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-verdent" }, { "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-emdash.json", "title": "Clawboo vs Emdash", "url": "https://www.anchorterminal.com/compare/clawboo-vs-emdash" }, { "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-emdash.json", "title": "CLI Manager vs Emdash", "url": "https://www.anchorterminal.com/compare/cli-manager-vs-emdash" }, { "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/emdash-vs-harness-autonomous.json", "title": "Emdash vs Harness", "url": "https://www.anchorterminal.com/compare/emdash-vs-harness-autonomous" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-paperclip.json", "title": "Emdash vs Paperclip", "url": "https://www.anchorterminal.com/compare/emdash-vs-paperclip" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-parallax-agents.json", "title": "Emdash vs Parallax", "url": "https://www.anchorterminal.com/compare/emdash-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": 2, "edge": "kiro-cli", "emdash": 55, "key": "reliability", "kiro-cli": 57, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 24, "edge": "kiro-cli", "emdash": 55, "key": "schema", "kiro-cli": 79, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 12, "edge": "kiro-cli", "emdash": 55, "key": "ergonomics", "kiro-cli": 67, "name": "Agent ergonomics", "weight": 13 }, { "by": 31, "edge": "kiro-cli", "emdash": 38, "key": "security", "kiro-cli": 69, "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "edge": "emdash", "emdash": 60, "key": "payments", "kiro-cli": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 3, "edge": "kiro-cli", "emdash": 70, "key": "maintenance", "kiro-cli": 73, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 17, "edge": "kiro-cli", "emdash": 54, "key": "transparency", "kiro-cli": 71, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Kiro CLI scores 59.8 (C) on agent readiness against Emdash's 53.9 (D), and leads in 6 of 7 scored categories. Emdash leads on payments \u0026 pricing. Both do agent harnesses.", "tasks": null, "tutorials": [], "verdicts": { "emdash": "A mature open-source app for parallel coding agents in Git worktrees, with issue intake from a dozen trackers and remote machines over SSH. Telemetry is on unless you turn it off, and no test workflow was found in the repository.", "kiro-cli": "Permission rules follow deny over ask over allow, and since 3.0.0 (3 November 2026) the V3 engine with workspace trust is the default. Content from Free and individual paid accounts is used for service improvement, including model training, unless the user opts out, and October releases fixed approval and Windows search-path flaws with no security advisory." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/emdash-vs-kiro-cli", "json": "https://www.anchorterminal.com/compare/emdash-vs-kiro-cli.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/emdash-vs-kiro-cli.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/emdash-vs-kiro-cli.min.md" }, "markdown": "Kiro CLI scores 59.8 (C) on agent readiness against Emdash's 53.9 (D), and leads in 6 of 7 scored categories. Emdash leads on payments \u0026 pricing. Both do agent harnesses.\n\n- Emdash: grade D, 53.9/100, rank #927 of 1486. Markdown https://www.anchorterminal.com/tools/emdash.md · JSON https://www.anchorterminal.com/api/v1/tools/emdash.json\n- Kiro CLI: grade C, 59.8/100, rank #675 of 1486. 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 1500 harnesses comparisons: https://www.anchorterminal.com/compare/agent-harnesses/index.md\n\n## Which one, for what\n\n### Emdash (D)\n\nGood for: Developers who want parallel agents in worktrees, fed from their issue tracker, locally or over SSH.\n\nAhead on:\n- Payments \u0026 pricing, 60 against 40\n\nAlso in its favour:\n- No key needed to call it\n- Open source\n- No incidents deducted, where Kiro CLI loses 5 points for them\n\nWatch for: Telemetry on unless turned off in Settings or with TELEMETRY_ENABLED=false\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- Schema \u0026 documentation, 79 against 55\n- Agent ergonomics, 67 against 55\n- Security \u0026 auth, 69 against 38\n- Transparency \u0026 trust, 71 against 54\n\nAlso in its favour:\n- Free to start without a card\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### Security \u0026 auth: Kiro CLI +31\n\n- Emdash (38): Harness reading. Telemetry is described as optional and disabled in Settings or with TELEMETRY_ENABLED=false, which reads as on by default (15 of 30). Worktree per task and remote machines over SSH (10 of 20). No prompt-injection guidance (5). No audit log (5). No security policy file found (3). 15 + 10 + 5 + 5 + 3 = 38.\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. V3 is the default since 3.0.0 (3 November 2026), interactive V3 sessions ask before loading a folder's hooks, agents and MCP servers since 2.33.0, and `/sandbox` puts agent shell commands and local stdio MCP servers in an operating-system sandbox. The sandbox is off unless chosen and doesn't cover the agent, built-in file tools or remote MCP servers, 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, 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 (Expires 2027-10-16) and kiro.dev/.well-known/security.txt answers 404, so 2 are held back for that and 2 for no bounty (16). 14+17+11+11+16 = 69.\n\n### Schema \u0026 documentation: Kiro CLI +24\n\n- Emdash (55): Harness reading. Docs site and a workspace server package (55).\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### Payments \u0026 pricing: Emdash +20\n\n- Emdash (60): Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60.\n- Kiro CLI (40): Harness reading of the published rubric, scored on the Kiro subscription the CLI needs. No payment protocol (0). Plan prices, the $0.04 credit price and per-model credit multipliers are public without a login (20). Kiro Free has 50 credits a month, and the pricing page asks for a card only on upgrade (20). A person signs in through a browser or device flow, and the API key for headless runs is created by hand at app.kiro.dev on a paid plan (0).\n\n### Transparency \u0026 trust: Kiro CLI +17\n\n- Emdash (54): Apache 2.0 (30). A telemetry page on the docs site (not read) (18 of 30). No deprecation policy (5). Disclosed with an opt-out (15 of 20). 30 + 18 + 5 + 15 = 68.\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, per the 8 October check (15). The data protection page (updated 23 October 2026) says what is stored for Free, individual and enterprise users, names US East (N. Virginia) for storage, 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, read on 8 October. No general retention period for stored content was found (22). The models page has a model lifecycle section with Experimental, Active and EOL stages and dates, and Claude Sonnet 4 ended on 14 October 2026. 3.0.0 made V3 the default as 2.30.0 announced and retired the Classic interface 34 days after the 2.26.0 deprecation notice, but the desktop app and inline autocomplete were retired in the same release with no earlier notice found, and no minimum notice period is stated (14). Telemetry types are listed and `kiro-cli settings telemetry.enabled` turns them off, with collection on by default. The data protection page's CLI steps still point to the desktop app's Preferences, which 3.0.0 retired (15). 15+22+14+15 = 66.\n\n### Agent ergonomics: Kiro CLI +12\n\n- Emdash (55): Harness reading. Issue intake from Linear, GitHub, Jira and others, diff review, pull requests and CI checks in one place, local or over SSH (55).\n- Kiro CLI (67): Framework reading, adapted to a harness driven by a pipeline. `--trust-tools` limits approved tools, `disabledTools` removes MCP tools per server, tool search loads MCP tools on demand, and custom agents carry their own tool set (20). Compaction and a workflow timeout (`KIRO_HEADLESS_WORKFLOW_TIMEOUT_SECS`, six hours by default) exist, but no cap on turns or run time for a plain headless run was found (10). Distinct exit codes for MCP startup failure and a missing agent, `--require-mcp-startup`, and a final interruption record in stream-json, with exit 1 for everything else (14). Sessions are saved every turn, with `--resume`, `--resume-id` and checkpoints with rewind (15). No SDK. The programmatic interfaces are the headless command and the ACP server, and a headless run needs a paid-plan API key and explicit trust flags (8).\n\n## Score by category\n\n| Category | Weight | Emdash | Kiro CLI | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 57 | Kiro CLI +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 55 | 79 | Kiro CLI +24 |\n| Agent ergonomics | 13% (16.2 this run) | 55 | 67 | Kiro CLI +12 |\n| Security \u0026 auth | 14% (17.5 this run) | 38 | 69 | Kiro CLI +31 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 40 | Emdash +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 70 | 73 | Kiro CLI +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 54 | 71 | Kiro CLI +17 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **53.9 · D** | **59.8 · C** | |\n\n## Facts side by side\n\n| Fact | Emdash | Kiro CLI |\n| --- | --- | --- |\n| Kind | Agent harness | Agent harness |\n| Vendor | General Action, Inc. | Amazon Web Services |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | None | OAuth or key |\n| Pricing | Free | Freemium |\n| x402 | no | no |\n| Licence | Apache-2.0 | 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-11-06 | 2026-11-03 |\n| Terms last updated | no document linked | 2026-08-14 |\n| Privacy policy last updated | no document linked | 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### Emdash\n\nNo score change since it was listed.\n\n### Kiro CLI\n\n- -1.0 on 3 November 2026: security\n- +0.1 on 28 October 2026: new evidence\n- +0.1 on 27 October 2026: checklist\n\n## Verdicts\n\n**Emdash.** A mature open-source app for parallel coding agents in Git worktrees, with issue intake from a dozen trackers and remote machines over SSH. Telemetry is on unless you turn it off, and no test workflow was found in the repository.\n\n**Kiro CLI.** Permission rules follow deny over ask over allow, and since 3.0.0 (3 November 2026) the V3 engine with workspace trust is the default. Content from Free and individual paid accounts is used for service improvement, including model training, unless the user opts out, and October releases fixed approval and Windows search-path flaws with no security advisory.\n\n## Before you call either\n\n### Emdash\n\n1. Launch with TELEMETRY_ENABLED=false if you don't want telemetry\n2. Use the SSH mode to keep agents on a remote machine\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. Run 2.34.0 or later. Earlier V3 headless runs could approve requests naming no trusted tool, and Windows hooks could run a planted program\n4. Run `kiro-cli settings telemetry.enabled false` and turn off content collection on Free and individual plans. Both are on by default\n5. Remove `autocomplete`, `inline`, `translate`, `theme` and `dashboard` from scripts, which 3.0.0 retired. Pass `--v2` to keep the V2 agent\n\n## Questions\n\n### Which is better for AI agents, Emdash or Kiro CLI?\n\nKiro CLI scores 59.8 (C) on agent readiness against Emdash's 53.9 (D), and leads in 6 of 7 scored categories. Emdash leads on payments \u0026 pricing.\n\n### Are Emdash and Kiro CLI open source?\n\nEmdash is open source (Apache-2.0). 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/emdash-vs-kiro-cli.json, and with the fewest tokens: https://www.anchorterminal.com/compare/emdash-vs-kiro-cli.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"emdash\", \"b\": \"kiro-cli\"}`. From a terminal: `anchor compare emdash kiro-cli`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/emdash.json and https://www.anchorterminal.com/api/v1/tools/kiro-cli.json\n\n## Other comparisons with Emdash or Kiro CLI\n\n- [Agent Zero vs Emdash](https://www.anchorterminal.com/compare/agent-zero-vs-emdash.md)\n- [Agent Zero vs Kiro CLI](https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli.md)\n- [Aider vs Emdash](https://www.anchorterminal.com/compare/aider-vs-emdash.md)\n- [Aider vs Kiro CLI](https://www.anchorterminal.com/compare/aider-vs-kiro-cli.md)\n- [Amp vs Emdash](https://www.anchorterminal.com/compare/amp-vs-emdash.md)\n- [Amp vs Kiro CLI](https://www.anchorterminal.com/compare/amp-vs-kiro-cli.md)\n- [Antigravity CLI vs Emdash](https://www.anchorterminal.com/compare/antigravity-cli-vs-emdash.md)\n- [Antigravity CLI vs Kiro CLI](https://www.anchorterminal.com/compare/antigravity-cli-vs-kiro-cli.md)\n- [Auggie CLI vs Emdash](https://www.anchorterminal.com/compare/auggie-vs-emdash.md)\n- [Auggie CLI vs Kiro CLI](https://www.anchorterminal.com/compare/auggie-vs-kiro-cli.md)\n- [AXLR vs Emdash](https://www.anchorterminal.com/compare/axlr-vs-emdash.md)\n- [AXLR vs Kiro CLI](https://www.anchorterminal.com/compare/axlr-vs-kiro-cli.md)\n- [Claude Code vs Emdash](https://www.anchorterminal.com/compare/claude-code-vs-emdash.md)\n- [Claude Code vs Kiro CLI](https://www.anchorterminal.com/compare/claude-code-vs-kiro-cli.md)\n- [Cline vs Emdash](https://www.anchorterminal.com/compare/cline-vs-emdash.md)\n- [Cline vs Kiro CLI](https://www.anchorterminal.com/compare/cline-vs-kiro-cli.md)\n- [Conductor vs Emdash](https://www.anchorterminal.com/compare/conductor-vs-emdash.md)\n- [Conductor vs Kiro CLI](https://www.anchorterminal.com/compare/conductor-vs-kiro-cli.md)\n- [Crush vs Emdash](https://www.anchorterminal.com/compare/crush-vs-emdash.md)\n- [Crush vs Kiro CLI](https://www.anchorterminal.com/compare/crush-vs-kiro-cli.md)\n- [Cursor CLI vs Emdash](https://www.anchorterminal.com/compare/cursor-cli-vs-emdash.md)\n- [Cursor CLI vs Kiro CLI](https://www.anchorterminal.com/compare/cursor-cli-vs-kiro-cli.md)\n- [DeepSeek Harness (dsh) vs Emdash](https://www.anchorterminal.com/compare/deepseek-harness-vs-emdash.md)\n- [DeepSeek Harness (dsh) vs Kiro CLI](https://www.anchorterminal.com/compare/deepseek-harness-vs-kiro-cli.md)\n- [dsh-superagent (DeepSeek) vs Emdash](https://www.anchorterminal.com/compare/deepseek-superagent-vs-emdash.md)\n- [dsh-superagent (DeepSeek) vs Kiro CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli.md)\n- [Devin vs Emdash](https://www.anchorterminal.com/compare/devin-vs-emdash.md)\n- [Devin vs Kiro CLI](https://www.anchorterminal.com/compare/devin-vs-kiro-cli.md)\n- [Droid CLI vs Emdash](https://www.anchorterminal.com/compare/droid-cli-vs-emdash.md)\n- [Droid CLI vs Kiro CLI](https://www.anchorterminal.com/compare/droid-cli-vs-kiro-cli.md)\n- [Pi vs Emdash](https://www.anchorterminal.com/compare/earendil-pi-vs-emdash.md)\n- [Pi vs Kiro CLI](https://www.anchorterminal.com/compare/earendil-pi-vs-kiro-cli.md)\n- [Emdash vs Gemini CLI](https://www.anchorterminal.com/compare/emdash-vs-gemini-cli.md)\n- [Emdash vs GitHub Copilot CLI](https://www.anchorterminal.com/compare/emdash-vs-github-copilot-cli.md)\n- [Emdash vs goose](https://www.anchorterminal.com/compare/emdash-vs-goose.md)\n- [Emdash vs Harness²](https://www.anchorterminal.com/compare/emdash-vs-harness2.md)\n- [Emdash vs HarnessRouter](https://www.anchorterminal.com/compare/emdash-vs-harnessrouter.md)\n- [Emdash vs Jules](https://www.anchorterminal.com/compare/emdash-vs-jules.md)\n- [Emdash vs Junie CLI](https://www.anchorterminal.com/compare/emdash-vs-junie.md)\n- [Emdash vs Kilo Code CLI](https://www.anchorterminal.com/compare/emdash-vs-kilo-code-cli.md)\n- [Emdash vs Kimi Code CLI](https://www.anchorterminal.com/compare/emdash-vs-kimi-code-cli.md)\n- [Emdash vs Letta](https://www.anchorterminal.com/compare/emdash-vs-letta.md)\n- [Emdash vs mini-swe-agent](https://www.anchorterminal.com/compare/emdash-vs-mini-swe-agent.md)\n- [Emdash vs MiniMax Code](https://www.anchorterminal.com/compare/emdash-vs-minimax-code.md)\n- [Emdash vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/emdash-vs-mistral-vibe-cli.md)\n- [Emdash vs Muse Code](https://www.anchorterminal.com/compare/emdash-vs-muse-code.md)\n- [Emdash vs OpenAI Agents API](https://www.anchorterminal.com/compare/emdash-vs-openai-agents-api.md)\n- [Emdash vs OpenAI Codex](https://www.anchorterminal.com/compare/emdash-vs-openai-codex.md)\n- [Emdash vs OpenCode](https://www.anchorterminal.com/compare/emdash-vs-opencode.md)\n- [Emdash vs OpenHands](https://www.anchorterminal.com/compare/emdash-vs-openhands.md)\n- [Emdash vs OpenMausBot](https://www.anchorterminal.com/compare/emdash-vs-openmausbot.md)\n- [Emdash vs Orca](https://www.anchorterminal.com/compare/emdash-vs-orca.md)\n- [Emdash vs Paseo](https://www.anchorterminal.com/compare/emdash-vs-paseo.md)\n- [Emdash vs Prime Agent](https://www.anchorterminal.com/compare/emdash-vs-prime-agent.md)\n- [Emdash vs Qoder CLI](https://www.anchorterminal.com/compare/emdash-vs-qoder-cli.md)\n- [Emdash vs Qwen Code](https://www.anchorterminal.com/compare/emdash-vs-qwen-code.md)\n- [Emdash vs Mirror CLI](https://www.anchorterminal.com/compare/emdash-vs-reflection-mirror.md)\n- [Emdash vs Rovo Dev CLI](https://www.anchorterminal.com/compare/emdash-vs-rovo-dev-cli.md)\n- [Emdash vs Sculptor](https://www.anchorterminal.com/compare/emdash-vs-sculptor.md)\n- [Emdash vs T3 Code](https://www.anchorterminal.com/compare/emdash-vs-t3-code.md)\n- [Emdash vs Traycer](https://www.anchorterminal.com/compare/emdash-vs-traycer.md)\n- [Emdash vs Unstoppable](https://www.anchorterminal.com/compare/emdash-vs-unstoppable.md)\n- [Emdash vs Verdent](https://www.anchorterminal.com/compare/emdash-vs-verdent.md)\n- [Emdash vs Vibe-Trading](https://www.anchorterminal.com/compare/emdash-vs-vibe-trading.md)\n- [Emdash vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/emdash-vs-warp.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 Letta](https://www.anchorterminal.com/compare/kiro-cli-vs-letta.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 Agents API](https://www.anchorterminal.com/compare/kiro-cli-vs-openai-agents-api.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 Orca](https://www.anchorterminal.com/compare/kiro-cli-vs-orca.md)\n- [Kiro CLI vs Paseo](https://www.anchorterminal.com/compare/kiro-cli-vs-paseo.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 Sculptor](https://www.anchorterminal.com/compare/kiro-cli-vs-sculptor.md)\n- [Kiro CLI vs T3 Code](https://www.anchorterminal.com/compare/kiro-cli-vs-t3-code.md)\n- [Kiro CLI vs Traycer](https://www.anchorterminal.com/compare/kiro-cli-vs-traycer.md)\n- [Kiro CLI vs Unstoppable](https://www.anchorterminal.com/compare/kiro-cli-vs-unstoppable.md)\n- [Kiro CLI vs Verdent](https://www.anchorterminal.com/compare/kiro-cli-vs-verdent.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 Emdash](https://www.anchorterminal.com/compare/clawboo-vs-emdash.md)\n- [Clawboo vs Kiro CLI](https://www.anchorterminal.com/compare/clawboo-vs-kiro-cli.md)\n- [CLI Manager vs Emdash](https://www.anchorterminal.com/compare/cli-manager-vs-emdash.md)\n- [CLI Manager vs Kiro CLI](https://www.anchorterminal.com/compare/cli-manager-vs-kiro-cli.md)\n- [Emdash vs Harness](https://www.anchorterminal.com/compare/emdash-vs-harness-autonomous.md)\n- [Emdash vs Paperclip](https://www.anchorterminal.com/compare/emdash-vs-paperclip.md)\n- [Emdash vs Parallax](https://www.anchorterminal.com/compare/emdash-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-07", "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": "Emdash vs Kiro CLI", "url": "" } ], "description": "Kiro CLI scores 59.8 (C) to Emdash's 53.9 (D) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Emdash D 53.9", "Kiro CLI C 59.8", "scores" ], "h1": "Emdash vs Kiro CLI", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/emdash-vs-kiro-cli", "published": "2026-10-01", "section": "tools", "title": "Emdash vs Kiro CLI for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/emdash-vs-kiro-cli" }, "tokens": { "markdown": 5800, "slim": 2280 }, "version": 1 }