{ "data": { "a": { "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" } }, "answer": "Kiro CLI scores 59.8 (C) on agent readiness against T3 Code's 51.9 (D), and leads in 5 of 7 scored categories. T3 Code leads on payments \u0026 pricing.", "b": { "slug": "t3-code", "name": "T3 Code", "vendor": "T3 Tools Inc.", "vendorUrl": "https://t3.codes", "kind": "harness", "category": "agent-harnesses", "summary": "T3 Code is an open-source control surface for the coding agents on your machine, Claude Code, Codex, Cursor, Grok Build, OpenCode, Antigravity and fx, from desktop, web and iOS and Android apps.", "url": "https://www.anchorterminal.com/tools/t3-code", "markdownUrl": "https://www.anchorterminal.com/tools/t3-code.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/t3-code.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/t3-code.json", "dns": "t3-code.grade.anchorterminal.com", "repo": "https://github.com/pingdotgg/t3code", "license": "MIT", "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://github.com/pingdotgg/t3code/tree/main/docs", "capabilities": [ "agent.harness", "agent.multi-agent" ], "tags": [ "open-source", "mit", "desktop-app", "mobile", "telemetry", "new" ], "lastRelease": "2026-11-06", "graded": true, "anchor": { "graded": true, "score": 51.9, "grade": "D", "agentReady": false, "rank": 1002, "ranked": true, "rankOf": 1486, "categoryRank": 40, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 60, "maintenance": 75, "payments": 60, "reliability": 43, "schema": 55, "security": 35, "transparency": 51 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-07" }, "negative": 0, "verdict": "A fast-moving open-source way to run and steer several coding agents from desktop, browser or phone, using the subscriptions you already have. It's pre-1.0, and it sends usage data by default, including hashed identifiers for your OpenAI and Claude accounts, with the opt-out documented outside the README.", "bestFor": "Developers who want one app, including on their phone, to drive several coding agents they already pay for.", "strengths": [ "Controls Claude Code, Codex, Cursor, Grok Build, OpenCode, Antigravity and fx with your existing subscriptions", "iOS and Android apps to steer agents running on your machine", "Managed policies for teams, including turning telemetry off", "MIT, with active CI and daily nightlies" ], "weaknesses": [ "Usage data on by default, with hashed OpenAI and Claude account identifiers, and relay traces to Axiom", "The telemetry opt-out is in the docs, not the README", "Pre-1.0, at 0.1.7 stable", "Installs with curl piped to sh" ], "agentNotes": [ "Set T3CODE_TELEMETRY_ENABLED=false before starting the server if you don't want usage events sent", "Install and log in to at least one provider CLI first, such as codex login or claude auth login", "Use a managed policy to fix settings across a team" ], "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": 51.9 } ], "editorialScores": { "ergonomics": 60, "maintenance": 75, "payments": 60, "reliability": 43, "schema": 55, "security": 35, "transparency": 62 }, "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": "curl -fsSL https://t3.codes/install.sh | sh" }, "letme": { "capability": "https://letme.dev/agent.harness", "tool": "https://letme.dev/t3-code" }, "area": "frameworks", "provenance": { "legalEntity": "T3 Tools Inc.", "domain": "t3.codes", "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 T3 Tools Inc.. The repository is github.com/pingdotgg/t3code." ], "score": 40 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/t3-code.json", "live": { "slug": "t3-code", "securityTxt": { "url": "https://t3.codes/.well-known/security.txt", "state": "valid", "expires": "2027-11-07T09:42:17.281Z", "checkedAt": "2026-11-07T16:01:55.404622007Z" }, "updatedAt": "2026-11-07T16:01:55.404622007Z" } }, "edges": [ { "by": 34, "category": "security", "leads": "kiro-cli", "name": "Security \u0026 auth", "reasons": { "a": "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.", "b": "Harness reading. Product usage events go by default to ingest.t3.codes and PostHog, with hashed identifiers for your T3 Connect, OpenAI and Claude accounts, and relay traces to Axiom, which can include machine names and error text. Off with T3CODE_TELEMETRY_ENABLED=false or a managed policy. Disclosed in docs/user/telemetry.md, not the README (10 of 30). Permission modes and managed policies (12 of 20). No prompt-injection guidance (5). No audit log (5). No security policy file found (3). 10 + 12 + 5 + 5 + 3 = 35." }, "scores": { "a": 69, "b": 35 } }, { "by": 24, "category": "schema", "leads": "kiro-cli", "name": "Schema \u0026 documentation", "reasons": { "a": "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).", "b": "Harness reading. User docs in the repository (managed policy, handoffs, providers, telemetry), AGENTS.md for contributors, a server other clients connect to (55)." }, "scores": { "a": 79, "b": 55 } }, { "by": 20, "category": "payments", "leads": "t3-code", "name": "Payments \u0026 pricing", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 40, "b": 60 } }, { "by": 20, "category": "transparency", "leads": "kiro-cli", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "MIT (30). docs/user/telemetry.md lists what is sent and what isn't, but includes hashed third-party account identifiers and the README doesn't mention it (15 of 30). No deprecation policy (5). Disclosed with an opt-out, on by default (12 of 20). 30 + 15 + 5 + 12 = 62." }, "scores": { "a": 71, "b": 51 } }, { "by": 14, "category": "reliability", "leads": "kiro-cli", "name": "Reliability", "reasons": { "a": "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, per the 8 October check (20). No public CI or test suite, since the source isn't published and the GitHub repository is an issue tracker whose newest commit is 27 August (0). Per the 8 October check, not re-read on 3 November, 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 (12). A dated changelog for every release, and 3.0.0 lists its breaking changes under their own heading with a migration route, though 2.24.0 stopped loading project `.env` files in a minor version (10). 3.0.0 on 3 November 2026 makes V3 the default engine (15). 20+0+12+10+15 = 57.", "b": "Local software. An install script and desktop and mobile apps from the vendor (20). ci.yml and windows-tests.yml run on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Stable tags v0.1.5 to v0.1.7 with many nightlies, no changelog file (8). Version 0.1.7 (0). 20 + 15 + 0 + 8 + 0 = 43." }, "scores": { "a": 57, "b": 43 } }, { "by": 7, "category": "ergonomics", "leads": "kiro-cli", "name": "Agent ergonomics", "reasons": { "a": "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).", "b": "Harness reading. Remote control from phone or browser, portable handoffs between providers and managed policies for teams (60)." }, "scores": { "a": 67, "b": 60 } } ], "facts": [ { "a": "Agent harness", "b": "Agent harness", "name": "Kind" }, { "a": "Amazon Web Services", "b": "T3 Tools Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "", "b": "", "name": "Transports" }, { "a": "OAuth or key", "b": "None", "name": "Auth" }, { "a": "Freemium", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-11-03", "b": "2026-11-06", "name": "Last release" }, { "a": "2026-08-14", "b": "no document linked", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not read yet", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "4.4k stars", "b": "none", "name": "Popularity" }, { "a": "2.8/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Kiro CLI scores 59.8 (C) on agent readiness against T3 Code's 51.9 (D), and leads in 5 of 7 scored categories. T3 Code leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Kiro CLI or T3 Code?" }, { "answer": "No open-source release is listed for Kiro CLI. T3 Code is open source (MIT).", "question": "Are Kiro CLI and T3 Code open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 57 against 43", "Schema \u0026 documentation, 79 against 55", "Agent ergonomics, 67 against 60", "Security \u0026 auth, 69 against 35", "Transparency \u0026 trust, 71 against 51" ], "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" }, { "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 one app, including on their phone, to drive several coding agents they already pay for.", "slug": "t3-code", "watchFor": "Usage data on by default, with hashed OpenAI and Claude account identifiers, and relay traces to Axiom" } ], "history": { "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" } ], "t3-code": null }, "job": { "capability": "agent.harness", "name": "Agent harnesses" }, "others": [ { "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/agent-zero-vs-t3-code.json", "title": "Agent Zero vs T3 Code", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-t3-code" }, { "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/aider-vs-t3-code.json", "title": "Aider vs T3 Code", "url": "https://www.anchorterminal.com/compare/aider-vs-t3-code" }, { "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/amp-vs-t3-code.json", "title": "Amp vs T3 Code", "url": "https://www.anchorterminal.com/compare/amp-vs-t3-code" }, { "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/antigravity-cli-vs-t3-code.json", "title": "Antigravity CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-t3-code" }, { "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/auggie-vs-t3-code.json", "title": "Auggie CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/auggie-vs-t3-code" }, { "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/axlr-vs-t3-code.json", "title": "AXLR vs T3 Code", "url": "https://www.anchorterminal.com/compare/axlr-vs-t3-code" }, { "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/claude-code-vs-t3-code.json", "title": "Claude Code vs T3 Code", "url": "https://www.anchorterminal.com/compare/claude-code-vs-t3-code" }, { "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/cline-vs-t3-code.json", "title": "Cline vs T3 Code", "url": "https://www.anchorterminal.com/compare/cline-vs-t3-code" }, { "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/conductor-vs-t3-code.json", "title": "Conductor vs T3 Code", "url": "https://www.anchorterminal.com/compare/conductor-vs-t3-code" }, { "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/crush-vs-t3-code.json", "title": "Crush vs T3 Code", "url": "https://www.anchorterminal.com/compare/crush-vs-t3-code" }, { "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/cursor-cli-vs-t3-code.json", "title": "Cursor CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/cursor-cli-vs-t3-code" }, { "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-harness-vs-t3-code.json", "title": "DeepSeek Harness (dsh) vs T3 Code", "url": "https://www.anchorterminal.com/compare/deepseek-harness-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli.json", "title": "dsh-superagent (DeepSeek) vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-t3-code.json", "title": "dsh-superagent (DeepSeek) vs T3 Code", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-t3-code" }, { "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/devin-vs-t3-code.json", "title": "Devin vs T3 Code", "url": "https://www.anchorterminal.com/compare/devin-vs-t3-code" }, { "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/droid-cli-vs-t3-code.json", "title": "Droid CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/droid-cli-vs-t3-code" }, { "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/earendil-pi-vs-t3-code.json", "title": "Pi vs T3 Code", "url": "https://www.anchorterminal.com/compare/earendil-pi-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/emdash-vs-kiro-cli.json", "title": "Emdash vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/emdash-vs-kiro-cli" }, { "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/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/gemini-cli-vs-t3-code.json", "title": "Gemini CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/gemini-cli-vs-t3-code" }, { "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/github-copilot-cli-vs-t3-code.json", "title": "GitHub Copilot CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-t3-code" }, { "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/goose-vs-t3-code.json", "title": "goose vs T3 Code", "url": "https://www.anchorterminal.com/compare/goose-vs-t3-code" }, { "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/harness2-vs-t3-code.json", "title": "Harness² vs T3 Code", "url": "https://www.anchorterminal.com/compare/harness2-vs-t3-code" }, { "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/harnessrouter-vs-t3-code.json", "title": "HarnessRouter vs T3 Code", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-t3-code" }, { "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/jules-vs-t3-code.json", "title": "Jules vs T3 Code", "url": "https://www.anchorterminal.com/compare/jules-vs-t3-code" }, { "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/junie-vs-t3-code.json", "title": "Junie CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/junie-vs-t3-code" }, { "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/kilo-code-cli-vs-t3-code.json", "title": "Kilo Code CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-kiro-cli.json", "title": "Kimi Code CLI vs Kiro CLI", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-kiro-cli" }, { "json": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-t3-code.json", "title": "Kimi Code CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-t3-code" }, { "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-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/letta-vs-t3-code.json", "title": "Letta vs T3 Code", "url": "https://www.anchorterminal.com/compare/letta-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/mini-swe-agent-vs-t3-code.json", "title": "mini-swe-agent vs T3 Code", "url": "https://www.anchorterminal.com/compare/mini-swe-agent-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/minimax-code-vs-t3-code.json", "title": "MiniMax Code vs T3 Code", "url": "https://www.anchorterminal.com/compare/minimax-code-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-t3-code.json", "title": "Mistral Vibe CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/muse-code-vs-t3-code.json", "title": "Muse Code vs T3 Code", "url": "https://www.anchorterminal.com/compare/muse-code-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-t3-code.json", "title": "OpenAI Agents API vs T3 Code", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/openai-codex-vs-t3-code.json", "title": "OpenAI Codex vs T3 Code", "url": "https://www.anchorterminal.com/compare/openai-codex-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/opencode-vs-t3-code.json", "title": "OpenCode vs T3 Code", "url": "https://www.anchorterminal.com/compare/opencode-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/openhands-vs-t3-code.json", "title": "OpenHands vs T3 Code", "url": "https://www.anchorterminal.com/compare/openhands-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/orca-vs-t3-code.json", "title": "Orca vs T3 Code", "url": "https://www.anchorterminal.com/compare/orca-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/paseo-vs-t3-code.json", "title": "Paseo vs T3 Code", "url": "https://www.anchorterminal.com/compare/paseo-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/prime-agent-vs-t3-code.json", "title": "Prime Agent vs T3 Code", "url": "https://www.anchorterminal.com/compare/prime-agent-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/qoder-cli-vs-t3-code.json", "title": "Qoder CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/qoder-cli-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/qwen-code-vs-t3-code.json", "title": "Qwen Code vs T3 Code", "url": "https://www.anchorterminal.com/compare/qwen-code-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/reflection-mirror-vs-t3-code.json", "title": "Mirror CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/reflection-mirror-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-t3-code.json", "title": "Rovo Dev CLI vs T3 Code", "url": "https://www.anchorterminal.com/compare/rovo-dev-cli-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/sculptor-vs-t3-code.json", "title": "Sculptor vs T3 Code", "url": "https://www.anchorterminal.com/compare/sculptor-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/t3-code-vs-traycer.json", "title": "T3 Code vs Traycer", "url": "https://www.anchorterminal.com/compare/t3-code-vs-traycer" }, { "json": "https://www.anchorterminal.com/compare/t3-code-vs-unstoppable.json", "title": "T3 Code vs Unstoppable", "url": "https://www.anchorterminal.com/compare/t3-code-vs-unstoppable" }, { "json": "https://www.anchorterminal.com/compare/t3-code-vs-verdent.json", "title": "T3 Code vs Verdent", "url": "https://www.anchorterminal.com/compare/t3-code-vs-verdent" }, { "json": "https://www.anchorterminal.com/compare/t3-code-vs-vibe-trading.json", "title": "T3 Code vs Vibe-Trading", "url": "https://www.anchorterminal.com/compare/t3-code-vs-vibe-trading" }, { "json": "https://www.anchorterminal.com/compare/t3-code-vs-warp.json", "title": "T3 Code vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/t3-code-vs-warp" }, { "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/clawboo-vs-t3-code.json", "title": "Clawboo vs T3 Code", "url": "https://www.anchorterminal.com/compare/clawboo-vs-t3-code" }, { "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/cli-manager-vs-t3-code.json", "title": "CLI Manager vs T3 Code", "url": "https://www.anchorterminal.com/compare/cli-manager-vs-t3-code" }, { "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/harness-autonomous-vs-t3-code.json", "title": "Harness vs T3 Code", "url": "https://www.anchorterminal.com/compare/harness-autonomous-vs-t3-code" }, { "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" }, { "json": "https://www.anchorterminal.com/compare/openmausbot-vs-t3-code.json", "title": "OpenMausBot vs T3 Code", "url": "https://www.anchorterminal.com/compare/openmausbot-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/paperclip-vs-t3-code.json", "title": "Paperclip vs T3 Code", "url": "https://www.anchorterminal.com/compare/paperclip-vs-t3-code" }, { "json": "https://www.anchorterminal.com/compare/parallax-agents-vs-t3-code.json", "title": "Parallax vs T3 Code", "url": "https://www.anchorterminal.com/compare/parallax-agents-vs-t3-code" } ], "panel": null, "scores": [ { "by": 14, "edge": "kiro-cli", "key": "reliability", "kiro-cli": 57, "name": "Reliability", "t3-code": 43, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 24, "edge": "kiro-cli", "key": "schema", "kiro-cli": 79, "name": "Schema \u0026 documentation", "t3-code": 55, "weight": 13 }, { "by": 7, "edge": "kiro-cli", "key": "ergonomics", "kiro-cli": 67, "name": "Agent ergonomics", "t3-code": 60, "weight": 13 }, { "by": 34, "edge": "kiro-cli", "key": "security", "kiro-cli": 69, "name": "Security \u0026 auth", "t3-code": 35, "weight": 14 }, { "by": 20, "edge": "t3-code", "key": "payments", "kiro-cli": 40, "name": "Payments \u0026 pricing", "t3-code": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 2, "edge": "t3-code", "key": "maintenance", "kiro-cli": 73, "name": "Maintenance \u0026 community", "t3-code": 75, "weight": 7 }, { "by": 20, "edge": "kiro-cli", "key": "transparency", "kiro-cli": 71, "name": "Transparency \u0026 trust", "t3-code": 51, "weight": 7 } ], "summary": "Kiro CLI scores 59.8 (C) on agent readiness against T3 Code's 51.9 (D), and leads in 5 of 7 scored categories. T3 Code leads on payments \u0026 pricing. Both do agent harnesses.", "tasks": null, "tutorials": [], "verdicts": { "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.", "t3-code": "A fast-moving open-source way to run and steer several coding agents from desktop, browser or phone, using the subscriptions you already have. It's pre-1.0, and it sends usage data by default, including hashed identifiers for your OpenAI and Claude accounts, with the opt-out documented outside the README." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/kiro-cli-vs-t3-code", "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-t3-code.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/kiro-cli-vs-t3-code.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/kiro-cli-vs-t3-code.min.md" }, "markdown": "Kiro CLI scores 59.8 (C) on agent readiness against T3 Code's 51.9 (D), and leads in 5 of 7 scored categories. T3 Code leads on payments \u0026 pricing. Both do agent harnesses.\n\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- T3 Code: grade D, 51.9/100, rank #1002 of 1486. Markdown https://www.anchorterminal.com/tools/t3-code.md · JSON https://www.anchorterminal.com/api/v1/tools/t3-code.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### 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 43\n- Schema \u0026 documentation, 79 against 55\n- Agent ergonomics, 67 against 60\n- Security \u0026 auth, 69 against 35\n- Transparency \u0026 trust, 71 against 51\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### T3 Code (D)\n\nGood for: Developers who want one app, including on their phone, to drive several coding agents they already pay for.\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: Usage data on by default, with hashed OpenAI and Claude account identifiers, and relay traces to Axiom\n\n\n## Why the edge\n\n### Security \u0026 auth: Kiro CLI +34\n\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- T3 Code (35): Harness reading. Product usage events go by default to ingest.t3.codes and PostHog, with hashed identifiers for your T3 Connect, OpenAI and Claude accounts, and relay traces to Axiom, which can include machine names and error text. Off with T3CODE_TELEMETRY_ENABLED=false or a managed policy. Disclosed in docs/user/telemetry.md, not the README (10 of 30). Permission modes and managed policies (12 of 20). No prompt-injection guidance (5). No audit log (5). No security policy file found (3). 10 + 12 + 5 + 5 + 3 = 35.\n\n### Schema \u0026 documentation: Kiro CLI +24\n\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- T3 Code (55): Harness reading. User docs in the repository (managed policy, handoffs, providers, telemetry), AGENTS.md for contributors, a server other clients connect to (55).\n\n### Payments \u0026 pricing: T3 Code +20\n\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- T3 Code (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\n### Transparency \u0026 trust: Kiro CLI +20\n\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- T3 Code (51): MIT (30). docs/user/telemetry.md lists what is sent and what isn't, but includes hashed third-party account identifiers and the README doesn't mention it (15 of 30). No deprecation policy (5). Disclosed with an opt-out, on by default (12 of 20). 30 + 15 + 5 + 12 = 62.\n\n### Reliability: Kiro CLI +14\n\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, per the 8 October check (20). No public CI or test suite, since the source isn't published and the GitHub repository is an issue tracker whose newest commit is 27 August (0). Per the 8 October check, not re-read on 3 November, 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 (12). A dated changelog for every release, and 3.0.0 lists its breaking changes under their own heading with a migration route, though 2.24.0 stopped loading project `.env` files in a minor version (10). 3.0.0 on 3 November 2026 makes V3 the default engine (15). 20+0+12+10+15 = 57.\n- T3 Code (43): Local software. An install script and desktop and mobile apps from the vendor (20). ci.yml and windows-tests.yml run on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Stable tags v0.1.5 to v0.1.7 with many nightlies, no changelog file (8). Version 0.1.7 (0). 20 + 15 + 0 + 8 + 0 = 43.\n\n### Agent ergonomics: Kiro CLI +7\n\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- T3 Code (60): Harness reading. Remote control from phone or browser, portable handoffs between providers and managed policies for teams (60).\n\n## Score by category\n\n| Category | Weight | Kiro CLI | T3 Code | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 57 | 43 | Kiro CLI +14 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 79 | 55 | Kiro CLI +24 |\n| Agent ergonomics | 13% (16.2 this run) | 67 | 60 | Kiro CLI +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 69 | 35 | Kiro CLI +34 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 60 | T3 Code +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 73 | 75 | T3 Code +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 51 | Kiro CLI +20 |\n| Negative events | ≤15 | -5 | 0 | |\n| **Total** | | **59.8 · C** | **51.9 · D** | |\n\n## Facts side by side\n\n| Fact | Kiro CLI | T3 Code |\n| --- | --- | --- |\n| Kind | Agent harness | Agent harness |\n| Vendor | Amazon Web Services | T3 Tools Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | | |\n| Auth | OAuth or key | None |\n| Pricing | Freemium | Free |\n| x402 | no | no |\n| Licence | 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 | MIT |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-11-03 | 2026-11-06 |\n| Terms last updated | 2026-08-14 | no document linked |\n| Privacy policy last updated | 2026-05-18 | no document linked |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | not found in the text | not read yet |\n| Terms restrict benchmarking | not found in the text | not read yet |\n| Terms or service can change without notice | not found in the text | not read yet |\n| Arbitration or class-action waiver | yes | not read yet |\n| Popularity | 4.4k stars | none |\n| Agent reviews | 2.8/5 (4) | none |\n\n## How the scores have moved\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### T3 Code\n\nNo score change since it was listed.\n\n## Verdicts\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**T3 Code.** A fast-moving open-source way to run and steer several coding agents from desktop, browser or phone, using the subscriptions you already have. It's pre-1.0, and it sends usage data by default, including hashed identifiers for your OpenAI and Claude accounts, with the opt-out documented outside the README.\n\n## Before you call either\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### T3 Code\n\n1. Set T3CODE_TELEMETRY_ENABLED=false before starting the server if you don't want usage events sent\n2. Install and log in to at least one provider CLI first, such as codex login or claude auth login\n3. Use a managed policy to fix settings across a team\n\n## Questions\n\n### Which is better for AI agents, Kiro CLI or T3 Code?\n\nKiro CLI scores 59.8 (C) on agent readiness against T3 Code's 51.9 (D), and leads in 5 of 7 scored categories. T3 Code leads on payments \u0026 pricing.\n\n### Are Kiro CLI and T3 Code open source?\n\nNo open-source release is listed for Kiro CLI. T3 Code is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/kiro-cli-vs-t3-code.json, and with the fewest tokens: https://www.anchorterminal.com/compare/kiro-cli-vs-t3-code.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"kiro-cli\", \"b\": \"t3-code\"}`. From a terminal: `anchor compare kiro-cli t3-code`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/kiro-cli.json and https://www.anchorterminal.com/api/v1/tools/t3-code.json\n\n## Other comparisons with Kiro CLI or T3 Code\n\n- [Agent Zero vs Kiro CLI](https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli.md)\n- [Agent Zero vs T3 Code](https://www.anchorterminal.com/compare/agent-zero-vs-t3-code.md)\n- [Aider vs Kiro CLI](https://www.anchorterminal.com/compare/aider-vs-kiro-cli.md)\n- [Aider vs T3 Code](https://www.anchorterminal.com/compare/aider-vs-t3-code.md)\n- [Amp vs Kiro CLI](https://www.anchorterminal.com/compare/amp-vs-kiro-cli.md)\n- [Amp vs T3 Code](https://www.anchorterminal.com/compare/amp-vs-t3-code.md)\n- [Antigravity CLI vs Kiro CLI](https://www.anchorterminal.com/compare/antigravity-cli-vs-kiro-cli.md)\n- [Antigravity CLI vs T3 Code](https://www.anchorterminal.com/compare/antigravity-cli-vs-t3-code.md)\n- [Auggie CLI vs Kiro CLI](https://www.anchorterminal.com/compare/auggie-vs-kiro-cli.md)\n- [Auggie CLI vs T3 Code](https://www.anchorterminal.com/compare/auggie-vs-t3-code.md)\n- [AXLR vs Kiro CLI](https://www.anchorterminal.com/compare/axlr-vs-kiro-cli.md)\n- [AXLR vs T3 Code](https://www.anchorterminal.com/compare/axlr-vs-t3-code.md)\n- [Claude Code vs Kiro CLI](https://www.anchorterminal.com/compare/claude-code-vs-kiro-cli.md)\n- [Claude Code vs T3 Code](https://www.anchorterminal.com/compare/claude-code-vs-t3-code.md)\n- [Cline vs Kiro CLI](https://www.anchorterminal.com/compare/cline-vs-kiro-cli.md)\n- [Cline vs T3 Code](https://www.anchorterminal.com/compare/cline-vs-t3-code.md)\n- [Conductor vs Kiro CLI](https://www.anchorterminal.com/compare/conductor-vs-kiro-cli.md)\n- [Conductor vs T3 Code](https://www.anchorterminal.com/compare/conductor-vs-t3-code.md)\n- [Crush vs Kiro CLI](https://www.anchorterminal.com/compare/crush-vs-kiro-cli.md)\n- [Crush vs T3 Code](https://www.anchorterminal.com/compare/crush-vs-t3-code.md)\n- [Cursor CLI vs Kiro CLI](https://www.anchorterminal.com/compare/cursor-cli-vs-kiro-cli.md)\n- [Cursor CLI vs T3 Code](https://www.anchorterminal.com/compare/cursor-cli-vs-t3-code.md)\n- [DeepSeek Harness (dsh) vs Kiro CLI](https://www.anchorterminal.com/compare/deepseek-harness-vs-kiro-cli.md)\n- [DeepSeek Harness (dsh) vs T3 Code](https://www.anchorterminal.com/compare/deepseek-harness-vs-t3-code.md)\n- [dsh-superagent (DeepSeek) vs Kiro CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli.md)\n- [dsh-superagent (DeepSeek) vs T3 Code](https://www.anchorterminal.com/compare/deepseek-superagent-vs-t3-code.md)\n- [Devin vs Kiro CLI](https://www.anchorterminal.com/compare/devin-vs-kiro-cli.md)\n- [Devin vs T3 Code](https://www.anchorterminal.com/compare/devin-vs-t3-code.md)\n- [Droid CLI vs Kiro CLI](https://www.anchorterminal.com/compare/droid-cli-vs-kiro-cli.md)\n- [Droid CLI vs T3 Code](https://www.anchorterminal.com/compare/droid-cli-vs-t3-code.md)\n- [Pi vs Kiro CLI](https://www.anchorterminal.com/compare/earendil-pi-vs-kiro-cli.md)\n- [Pi vs T3 Code](https://www.anchorterminal.com/compare/earendil-pi-vs-t3-code.md)\n- [Emdash vs Kiro CLI](https://www.anchorterminal.com/compare/emdash-vs-kiro-cli.md)\n- [Emdash vs T3 Code](https://www.anchorterminal.com/compare/emdash-vs-t3-code.md)\n- [Gemini CLI vs Kiro CLI](https://www.anchorterminal.com/compare/gemini-cli-vs-kiro-cli.md)\n- [Gemini CLI vs T3 Code](https://www.anchorterminal.com/compare/gemini-cli-vs-t3-code.md)\n- [GitHub Copilot CLI vs Kiro CLI](https://www.anchorterminal.com/compare/github-copilot-cli-vs-kiro-cli.md)\n- [GitHub Copilot CLI vs T3 Code](https://www.anchorterminal.com/compare/github-copilot-cli-vs-t3-code.md)\n- [goose vs Kiro CLI](https://www.anchorterminal.com/compare/goose-vs-kiro-cli.md)\n- [goose vs T3 Code](https://www.anchorterminal.com/compare/goose-vs-t3-code.md)\n- [Harness² vs Kiro CLI](https://www.anchorterminal.com/compare/harness2-vs-kiro-cli.md)\n- [Harness² vs T3 Code](https://www.anchorterminal.com/compare/harness2-vs-t3-code.md)\n- [HarnessRouter vs Kiro CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-kiro-cli.md)\n- [HarnessRouter vs T3 Code](https://www.anchorterminal.com/compare/harnessrouter-vs-t3-code.md)\n- [Jules vs Kiro CLI](https://www.anchorterminal.com/compare/jules-vs-kiro-cli.md)\n- [Jules vs T3 Code](https://www.anchorterminal.com/compare/jules-vs-t3-code.md)\n- [Junie CLI vs Kiro CLI](https://www.anchorterminal.com/compare/junie-vs-kiro-cli.md)\n- [Junie CLI vs T3 Code](https://www.anchorterminal.com/compare/junie-vs-t3-code.md)\n- [Kilo Code CLI vs Kiro CLI](https://www.anchorterminal.com/compare/kilo-code-cli-vs-kiro-cli.md)\n- [Kilo Code CLI vs T3 Code](https://www.anchorterminal.com/compare/kilo-code-cli-vs-t3-code.md)\n- [Kimi Code CLI vs Kiro CLI](https://www.anchorterminal.com/compare/kimi-code-cli-vs-kiro-cli.md)\n- [Kimi Code CLI vs T3 Code](https://www.anchorterminal.com/compare/kimi-code-cli-vs-t3-code.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 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- [Letta vs T3 Code](https://www.anchorterminal.com/compare/letta-vs-t3-code.md)\n- [mini-swe-agent vs T3 Code](https://www.anchorterminal.com/compare/mini-swe-agent-vs-t3-code.md)\n- [MiniMax Code vs T3 Code](https://www.anchorterminal.com/compare/minimax-code-vs-t3-code.md)\n- [Mistral Vibe CLI vs T3 Code](https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-t3-code.md)\n- [Muse Code vs T3 Code](https://www.anchorterminal.com/compare/muse-code-vs-t3-code.md)\n- [OpenAI Agents API vs T3 Code](https://www.anchorterminal.com/compare/openai-agents-api-vs-t3-code.md)\n- [OpenAI Codex vs T3 Code](https://www.anchorterminal.com/compare/openai-codex-vs-t3-code.md)\n- [OpenCode vs T3 Code](https://www.anchorterminal.com/compare/opencode-vs-t3-code.md)\n- [OpenHands vs T3 Code](https://www.anchorterminal.com/compare/openhands-vs-t3-code.md)\n- [Orca vs T3 Code](https://www.anchorterminal.com/compare/orca-vs-t3-code.md)\n- [Paseo vs T3 Code](https://www.anchorterminal.com/compare/paseo-vs-t3-code.md)\n- [Prime Agent vs T3 Code](https://www.anchorterminal.com/compare/prime-agent-vs-t3-code.md)\n- [Qoder CLI vs T3 Code](https://www.anchorterminal.com/compare/qoder-cli-vs-t3-code.md)\n- [Qwen Code vs T3 Code](https://www.anchorterminal.com/compare/qwen-code-vs-t3-code.md)\n- [Mirror CLI vs T3 Code](https://www.anchorterminal.com/compare/reflection-mirror-vs-t3-code.md)\n- [Rovo Dev CLI vs T3 Code](https://www.anchorterminal.com/compare/rovo-dev-cli-vs-t3-code.md)\n- [Sculptor vs T3 Code](https://www.anchorterminal.com/compare/sculptor-vs-t3-code.md)\n- [T3 Code vs Traycer](https://www.anchorterminal.com/compare/t3-code-vs-traycer.md)\n- [T3 Code vs Unstoppable](https://www.anchorterminal.com/compare/t3-code-vs-unstoppable.md)\n- [T3 Code vs Verdent](https://www.anchorterminal.com/compare/t3-code-vs-verdent.md)\n- [T3 Code vs Vibe-Trading](https://www.anchorterminal.com/compare/t3-code-vs-vibe-trading.md)\n- [T3 Code vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/t3-code-vs-warp.md)\n- [Clawboo vs Kiro CLI](https://www.anchorterminal.com/compare/clawboo-vs-kiro-cli.md)\n- [Clawboo vs T3 Code](https://www.anchorterminal.com/compare/clawboo-vs-t3-code.md)\n- [CLI Manager vs Kiro CLI](https://www.anchorterminal.com/compare/cli-manager-vs-kiro-cli.md)\n- [CLI Manager vs T3 Code](https://www.anchorterminal.com/compare/cli-manager-vs-t3-code.md)\n- [Harness vs Kiro CLI](https://www.anchorterminal.com/compare/harness-autonomous-vs-kiro-cli.md)\n- [Harness vs T3 Code](https://www.anchorterminal.com/compare/harness-autonomous-vs-t3-code.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- [OpenMausBot vs T3 Code](https://www.anchorterminal.com/compare/openmausbot-vs-t3-code.md)\n- [Paperclip vs T3 Code](https://www.anchorterminal.com/compare/paperclip-vs-t3-code.md)\n- [Parallax vs T3 Code](https://www.anchorterminal.com/compare/parallax-agents-vs-t3-code.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": "Kiro CLI vs T3 Code", "url": "" } ], "description": "Kiro CLI scores 59.8 (C) to T3 Code's 51.9 (D) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Kiro CLI C 59.8", "T3 Code D 51.9", "scores" ], "h1": "Kiro CLI vs T3 Code", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/kiro-cli-vs-t3-code", "published": "2026-10-01", "section": "tools", "title": "Kiro CLI vs T3 Code for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-t3-code" }, "tokens": { "markdown": 6350, "slim": 2730 }, "version": 1 }