{ "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": 610, "ranked": true, "rankOf": 1354, "categoryRank": 16, "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": 4448, "securityTxt": { "url": "https://kiro.dev/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-05T15:55:35.079615995Z" }, "llmsTxt": { "url": "https://kiro.dev/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-05T15:26:20.191724934Z" }, "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": 304, "checkedAt": "2026-11-05T12:57:21.404875489Z", "changedAt": "2026-11-04T08:25:55.789210293Z", "fingerprint": "19c1087b1982" }, { "url": "https://kiro.dev/changelog/cli/3-0/", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-05T12:57:23.536277316Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4e73d6a38bd8" }, { "url": "https://kiro.dev/changelog/models/", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-05T12:57:25.518996121Z", "changedAt": "2026-11-01T06:46:11.963005202Z", "fingerprint": "72ff67f24110" } ], "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-05T21:40:43.121070165Z" } }, "answer": "OpenAI Agents API scores 73.3 (BB) on agent readiness against Kiro CLI's 59.8 (C), and leads in 6 of 7 scored categories. Kiro CLI leads on payments \u0026 pricing.", "b": { "slug": "openai-agents-api", "name": "OpenAI Agents API", "vendor": "OpenAI", "vendorUrl": "https://openai.com/index/introducing-the-agents-api/", "kind": "http-api", "category": "agent-harnesses", "summary": "The OpenAI Agents API runs OpenAI's managed Codex harness as a hosted service. One call creates a session with a model, tools, MCP servers, subagents and an OpenAI-hosted or self-hosted sandbox, and OpenAI runs the loop.", "url": "https://www.anchorterminal.com/tools/openai-agents-api", "markdownUrl": "https://www.anchorterminal.com/tools/openai-agents-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/openai-agents-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/openai-agents-api.json", "dns": "openai-agents-api.grade.anchorterminal.com", "license": "Proprietary hosted API under OpenAI's Services Agreement. The SDKs are Apache 2.0", "transports": [ "https" ], "remoteUrl": "https://api.openai.com/v1/agents/sessions", "packages": [ { "registry": "pypi", "name": "openai" }, { "registry": "npm", "name": "openai" } ], "auth": "api-key", "authNotes": "An OpenAI project API key as a Bearer token, with the header `OpenAI-Beta: agents=v1`. Project keys can be restricted per endpoint or read-only, and service accounts and workload identity federation are available, per the openai-api listing. Signing up and creating a key need a person in a browser.", "pricing": "usage", "pricingNotes": "No fee for the API itself. Model tokens are billed at the chosen model's API rates, OpenAI tools at their built-in rates (web search $10.00 per 1,000 calls plus content tokens), and OpenAI-hosted sandboxes at container rates, $0.03 for 1 GB, $0.12 for 4 GB, $0.48 for 16 GB and $1.92 for 64 GB per 20-minute session, billed by the minute with a 5-minute minimum. Since 9 October sandbox compute is billed only during active turns (checked 2026-11-06).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Agents API guides or on OpenAI's pricing page; billing is to an OpenAI account (checked 2026-11-06).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://developers.openai.com/api/docs/guides/agents-api/overview", "llmsTxt": "https://developers.openai.com/api/docs/llms.txt", "capabilities": [ "agent.harness" ], "tags": [ "official", "hosted", "beta", "usage-priced", "llms-txt", "status-page", "mcp-client", "sandbox", "subagents", "webhooks", "soc2", "iso27001", "bug-bounty" ], "lastRelease": "2026-10-16", "graded": true, "anchor": { "graded": true, "score": 73.3, "grade": "BB", "agentReady": true, "rank": 99, "ranked": true, "rankOf": 1354, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 87, "payments": 30, "reliability": 60, "schema": 88, "security": 87, "transparency": 85 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "OpenAI's hosted agent runtime, the Codex harness behind one session call, with MCP, functions, web search, computer use, subagents and sandboxes on OpenAI or your own infrastructure. Documentation, errors and SDKs are thorough. It's still public beta, can't use Zero Data Retention and keeps data in the United States only.", "bestFor": "Teams that want OpenAI to run the agent loop, with sandboxes, MCP tools and subagents, and are fine with a beta API, US-only data residency and no Zero Data Retention.", "strengths": [ "One session call configures the model, tools, MCP servers, subagents and the sandbox, and OpenAI runs and recovers the loop", "Sandboxes on OpenAI or self-hosted, with guides for ten providers including E2B, Daytona, Modal, Cloudflare and Vercel", "An errors guide with codes per status and turn, Retry-After and a check-before-retry procedure", "Webhooks, streamed events, tracing and usage views for each session", "SDK examples in Python, JavaScript, Go, Java and Ruby", "Status page with its own Agents component" ], "weaknesses": [ "Public beta since 10 September 2026 behind the agents=v1 beta header, with no GA date", "Not eligible for Zero Data Retention, and data residency is United States only", "No idempotency key for session or turn requests; retries depend on checking state first", "One API-wide major outage on 29 September included it, plus several smaller incidents since release", "No retention period stated for published artifacts after a sandbox expires" ], "agentNotes": [ "POST https://api.openai.com/v1/agents/sessions with a project key and the header OpenAI-Beta: agents=v1, or use client.beta.agents in the SDKs", "Before retrying, retrieve the session and turn and check which actions completed, since there's no idempotency key", "Set the sandbox network to restricted with an allowlist of up to 100 hosts when the agent doesn't need the open web", "Save files from /workspace/outputs before deleting a session; no retention period is stated for artifacts", "Don't send data that needs Zero Data Retention or non-US residency; the Agents API supports neither" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 73.3 } ], "editorialScores": { "ergonomics": 80, "maintenance": 87, "payments": 30, "reliability": 60, "schema": 88, "security": 87, "transparency": 75 }, "provenanceScore": 95, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.openai.com/v1/agents/sessions \\\n -H \"Authorization: Bearer $OPENAI_API_KEY\" \\\n -H \"OpenAI-Beta: agents=v1\" \\\n -H \"Content-Type: application/json\" \\\n -d @session.json # model, tools, environment and input, per the quickstart" }, "letme": { "capability": "https://letme.dev/agent.harness", "tool": "https://letme.dev/openai-agents-api" }, "sameCompany": [ "openai-api", "openai-embeddings", "openai-guardrails", "openai-moderation", "openai-image-api", "openai-sora", "openai-speech-to-text", "gpt-live", "openai-realtime", "openai-agents-sdk", "openai-decisions-api", "openai-codex", "gpt-oss-120b", "gpt-oss-20b" ], "area": "frameworks", "provenance": { "legalEntity": "OpenAI OpCo, LLC", "domain": "openai.com", "domainRegistered": "2007-01-19", "domainNote": "openai.com was registered in 2007, before OpenAI existed, per the openai-api listing.", "endpointOnVendorDomain": true, "terms": "https://openai.com/policies/services-agreement/", "privacy": "https://openai.com/policies/privacy-policy/", "statusPage": "https://status.openai.com", "changelog": "https://developers.openai.com/api/docs/changelog", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "The endpoint is on api.openai.com, the same host as the rest of the OpenAI API. Terms, privacy, security.txt and the domain are the openai-api listing's readings." ], "score": 95 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/openai-agents-api.json", "live": { "slug": "openai-agents-api", "probe": { "target": "https://api.openai.com/v1/agents/sessions", "method": "get", "lastAt": "2026-11-06T09:47:41.371658489Z", "lastOk": true, "lastStatus": 400, "lastMs": 162, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 148, "p95ms24h": 166, "samples24h": 47, "samples30d": 47, "days": [ { "date": "2026-11-06", "probes": 47, "ok": 47 } ] }, "vendorStatus": { "page": "https://status.openai.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-06T09:43:26.425829944Z" }, "updatedAt": "2026-11-06T09:47:41.371658489Z" } }, "edges": [ { "by": 18, "category": "security", "leads": "openai-agents-api", "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": "Project keys with restricted per-endpoint permissions, service accounts and workload identity, per the openai-api listing; we didn't confirm a key can be limited to /v1/agents (27 of 30). Automatic review for approvals, a sandbox network restricted to a host allowlist, vaults for secrets and a sandbox security guide (17 of 20). The agent reads web pages, MCP results and browser content; the sandbox security guide and approval flow are the mitigations, with no prompt-injection guide of its own found (8 of 15). Tracing, observability and usage per session and admin audit logs (15). SOC 2 Type 2, ISO 27001 family, Bugcrowd bounty and a disclosure policy, per the openai-api listing (20). Not ZDR-eligible and US residency only, recorded under transparency. 27 + 17 + 8 + 15 + 20 = 87." }, "scores": { "a": 69, "b": 87 } }, { "by": 14, "category": "maintenance", "leads": "openai-agents-api", "name": "Maintenance \u0026 community", "reasons": { "a": "3.0.0 on 3 November 2026, after 2.37.1 on 31 October (30). 25 dated releases from 2.17.0 on 11 August to 3.0.0 on 3 November, plus five patches, read from the first three changelog pages back to 9 July (20). A public issue tracker with area labels and triage automation, 69 cli issues closed against 96 opened in the 30 days to 8 October, and a Discord server, per the 8 October check, not re-read on 3 November. We didn't establish how many replies come from staff (14). No SDK and no registry entry. The ACP server is kept current, with ACP sign-in added in 2.37.0 and a migration guide for clients moving to V3 (6). Closed source, so no CI or dependency health to read. The installer verifies checksums (3). 30+20+14+6+3 = 73.", "b": "Closed API. Last dated change 16 October 2026, Ultrafast mode and document skills (30). Four dated changelog entries in the 57 days since release, 10 September, 29 September, 9 October and 16 October (20). Changelog and help centre, as the openai-api listing reads them (12 of 15). Official SDKs carry beta.agents (15). SDK CI, per the openai-api listing (10). 30 + 20 + 12 + 15 + 10 = 87." }, "scores": { "a": 73, "b": 87 } }, { "by": 14, "category": "transparency", "leads": "openai-agents-api", "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": "Closed service with clear terms, Apache-2.0 SDKs (15). Session state retained until deleted, deletable sessions and artifacts, not ZDR-eligible, US residency only, and the data-controls guide agrees; no retention period for artifacts after a sandbox expires (25 of 30). Dated deprecation notices with minimum periods for GA models; a beta API can change faster (15 of 20). Subprocessors and processing countries listed, per the openai-api listing (20). 15 + 25 + 15 + 20 = 75." }, "scores": { "a": 71, "b": 85 } }, { "by": 13, "category": "ergonomics", "leads": "openai-agents-api", "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": "Read as an API an agent drives. Context is compacted automatically, and session budgets and streamed events keep output sized (20 of 25). Sessions can be listed, continued and steered, events streamed or sent by webhook, artifacts fetched (15 of 20). Actionable error codes with recovery steps (20). No idempotency key; a documented check-then-retry procedure (10 of 20). One session call with defaults (medium sandbox, network enabled), SDKs in five languages (15). 20 + 15 + 20 + 10 + 15 = 80." }, "scores": { "a": 67, "b": 80 } }, { "by": 10, "category": "payments", "leads": "kiro-cli", "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": "No machine payment protocol (0). Model, tool and container prices published without a login, and no fee for the API itself (20). The Free tier reading of the openai-api listing, half (10). Sign-up in a browser (0). 0 + 20 + 10 + 0 = 30." }, "scores": { "a": 40, "b": 30 } }, { "by": 9, "category": "schema", "leads": "openai-agents-api", "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": "The reference is linked from the overview and the SDKs carry beta.agents types; we didn't confirm /agents/sessions in OpenAI's public OpenAPI file, so 15 of 25. llms.txt with every Agents API page and Markdown twins (10). The overview, architecture page and the agents guide that compares the Agents API, Agents SDK and Responses API say when to use it (20). Typed configuration with enumerated container sizes, network modes and environment types (13 of 15). Examples in six languages and an errors page with codes per HTTP status, turn and session (15). Dated changelog entries and a versioned beta header (15). 15 + 10 + 20 + 13 + 15 + 15 = 88." }, "scores": { "a": 79, "b": 88 } } ], "facts": [ { "a": "Agent harness", "b": "HTTP API", "name": "Kind" }, { "a": "Amazon Web Services", "b": "OpenAI", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.openai.com/v1/agents/sessions", "name": "Hosted endpoint" }, { "a": "", "b": "https", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "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": "Proprietary hosted API under OpenAI's Services Agreement. The SDKs are Apache 2.0", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-11-03", "b": "2026-10-16", "name": "Last release" }, { "a": "2026-08-14", "b": "couldn't be read", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "couldn't be read", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "couldn't be read", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "couldn't be read", "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": "OpenAI Agents API scores 73.3 (BB) on agent readiness against Kiro CLI's 59.8 (C), and leads in 6 of 7 scored categories. Kiro CLI leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Kiro CLI or OpenAI Agents API?" }, { "answer": "No hosted endpoint is listed for Kiro CLI. OpenAI Agents API has a hosted endpoint at https://api.openai.com/v1/agents/sessions.", "question": "Can an agent call Kiro CLI and OpenAI Agents API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 40 against 30" ], "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": [ "Schema \u0026 documentation, 88 against 79", "Agent ergonomics, 80 against 67", "Security \u0026 auth, 87 against 69", "Maintenance \u0026 community, 87 against 73", "Transparency \u0026 trust, 85 against 71" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install", "No incidents deducted, where Kiro CLI loses 5 points for them" ], "goodFor": "Teams that want OpenAI to run the agent loop, with sandboxes, MCP tools and subagents, and are fine with a beta API, US-only data residency and no Zero Data Retention.", "slug": "openai-agents-api", "watchFor": "Public beta since 10 September 2026 behind the agents=v1 beta header, with no GA date" } ], "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" } ], "openai-agents-api": 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-openai-agents-api.json", "title": "Agent Zero vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/agent-zero-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Aider vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/aider-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Amp vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/amp-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Antigravity CLI vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/antigravity-cli-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Auggie CLI vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/auggie-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "AXLR vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/axlr-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Claude Code vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/claude-code-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Cline vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/cline-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Crush vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/crush-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Cursor CLI vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/cursor-cli-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "DeepSeek Harness (dsh) vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/deepseek-harness-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "dsh-superagent (DeepSeek) vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/deepseek-superagent-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Devin vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/devin-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Droid CLI vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/droid-cli-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Pi vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/earendil-pi-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Gemini CLI vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/gemini-cli-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "GitHub Copilot CLI vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/github-copilot-cli-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "goose vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/goose-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Harness² vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/harness2-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "HarnessRouter vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/harnessrouter-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Jules vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/jules-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Junie CLI vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/junie-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Kilo Code CLI vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/kilo-code-cli-vs-openai-agents-api" }, { "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-openai-agents-api.json", "title": "Kimi Code CLI vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/kimi-code-cli-vs-openai-agents-api" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-mini-swe-agent.json", "title": "Kiro CLI vs mini-swe-agent", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-mini-swe-agent" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-minimax-code.json", "title": "Kiro CLI vs MiniMax Code", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-minimax-code" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-mistral-vibe-cli.json", "title": "Kiro CLI vs Mistral Vibe CLI", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-mistral-vibe-cli" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-muse-code.json", "title": "Kiro CLI vs Muse Code", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-muse-code" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-codex.json", "title": "Kiro CLI vs OpenAI Codex", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-codex" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-opencode.json", "title": "Kiro CLI vs OpenCode", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-opencode" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-openhands.json", "title": "Kiro CLI vs OpenHands", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openhands" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-openmausbot.json", "title": "Kiro CLI vs OpenMausBot", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openmausbot" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-prime-agent.json", "title": "Kiro CLI vs Prime Agent", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-prime-agent" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-qoder-cli.json", "title": "Kiro CLI vs Qoder CLI", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-qoder-cli" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-qwen-code.json", "title": "Kiro CLI vs Qwen Code", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-qwen-code" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-reflection-mirror.json", "title": "Kiro CLI vs Mirror CLI", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-reflection-mirror" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli.json", "title": "Kiro CLI vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-unstoppable.json", "title": "Kiro CLI vs Unstoppable", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-unstoppable" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-vibe-trading.json", "title": "Kiro CLI vs Vibe-Trading", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-vibe-trading" }, { "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-warp.json", "title": "Kiro CLI vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-warp" }, { "json": "https://www.anchorterminal.com/compare/mini-swe-agent-vs-openai-agents-api.json", "title": "mini-swe-agent vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/mini-swe-agent-vs-openai-agents-api" }, { "json": "https://www.anchorterminal.com/compare/minimax-code-vs-openai-agents-api.json", "title": "MiniMax Code vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/minimax-code-vs-openai-agents-api" }, { "json": "https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-openai-agents-api.json", "title": "Mistral Vibe CLI vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-openai-agents-api" }, { "json": "https://www.anchorterminal.com/compare/muse-code-vs-openai-agents-api.json", "title": "Muse Code vs OpenAI Agents API", "url": "https://www.anchorterminal.com/compare/muse-code-vs-openai-agents-api" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-openai-codex.json", "title": "OpenAI Agents API vs OpenAI Codex", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-openai-codex" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-opencode.json", "title": "OpenAI Agents API vs OpenCode", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-opencode" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-openhands.json", "title": "OpenAI Agents API vs OpenHands", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-openhands" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-openmausbot.json", "title": "OpenAI Agents API vs OpenMausBot", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-openmausbot" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-prime-agent.json", "title": "OpenAI Agents API vs Prime Agent", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-prime-agent" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-qoder-cli.json", "title": "OpenAI Agents API vs Qoder CLI", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-qoder-cli" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-qwen-code.json", "title": "OpenAI Agents API vs Qwen Code", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-qwen-code" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-reflection-mirror.json", "title": "OpenAI Agents API vs Mirror CLI", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-reflection-mirror" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-rovo-dev-cli.json", "title": "OpenAI Agents API vs Rovo Dev CLI", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-rovo-dev-cli" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-unstoppable.json", "title": "OpenAI Agents API vs Unstoppable", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-unstoppable" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-vibe-trading.json", "title": "OpenAI Agents API vs Vibe-Trading", "url": "https://www.anchorterminal.com/compare/openai-agents-api-vs-vibe-trading" }, { "json": "https://www.anchorterminal.com/compare/openai-agents-api-vs-warp.json", "title": "OpenAI Agents API vs Warp (Warp Agent CLI and the Oz Agent API)", "url": "https://www.anchorterminal.com/compare/openai-agents-api-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/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/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": 3, "edge": "openai-agents-api", "key": "reliability", "kiro-cli": 57, "name": "Reliability", "openai-agents-api": 60, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 9, "edge": "openai-agents-api", "key": "schema", "kiro-cli": 79, "name": "Schema \u0026 documentation", "openai-agents-api": 88, "weight": 13 }, { "by": 13, "edge": "openai-agents-api", "key": "ergonomics", "kiro-cli": 67, "name": "Agent ergonomics", "openai-agents-api": 80, "weight": 13 }, { "by": 18, "edge": "openai-agents-api", "key": "security", "kiro-cli": 69, "name": "Security \u0026 auth", "openai-agents-api": 87, "weight": 14 }, { "by": 10, "edge": "kiro-cli", "key": "payments", "kiro-cli": 40, "name": "Payments \u0026 pricing", "openai-agents-api": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 14, "edge": "openai-agents-api", "key": "maintenance", "kiro-cli": 73, "name": "Maintenance \u0026 community", "openai-agents-api": 87, "weight": 7 }, { "by": 14, "edge": "openai-agents-api", "key": "transparency", "kiro-cli": 71, "name": "Transparency \u0026 trust", "openai-agents-api": 85, "weight": 7 } ], "summary": "OpenAI Agents API scores 73.3 (BB) on agent readiness against Kiro CLI's 59.8 (C), and leads in 6 of 7 scored categories. Kiro CLI 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.", "openai-agents-api": "OpenAI's hosted agent runtime, the Codex harness behind one session call, with MCP, functions, web search, computer use, subagents and sandboxes on OpenAI or your own infrastructure. Documentation, errors and SDKs are thorough. It's still public beta, can't use Zero Data Retention and keeps data in the United States only." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-agents-api", "json": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-agents-api.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-agents-api.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-agents-api.min.md" }, "markdown": "OpenAI Agents API scores 73.3 (BB) on agent readiness against Kiro CLI's 59.8 (C), and leads in 6 of 7 scored categories. Kiro CLI leads on payments \u0026 pricing. Both do agent harnesses.\n\n- Kiro CLI: grade C, 59.8/100, rank #610 of 1354. Markdown https://www.anchorterminal.com/tools/kiro-cli.md · JSON https://www.anchorterminal.com/api/v1/tools/kiro-cli.json\n- OpenAI Agents API: grade BB, 73.3/100, rank #99 of 1354. Markdown https://www.anchorterminal.com/tools/openai-agents-api.md · JSON https://www.anchorterminal.com/api/v1/tools/openai-agents-api.json\n- Best agent harnesses and coding agents: https://www.anchorterminal.com/best/agent-harnesses/index.md\n- All 1041 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- Payments \u0026 pricing, 40 against 30\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### OpenAI Agents API (BB)\n\nGood for: Teams that want OpenAI to run the agent loop, with sandboxes, MCP tools and subagents, and are fine with a beta API, US-only data residency and no Zero Data Retention.\n\nAhead on:\n- Schema \u0026 documentation, 88 against 79\n- Agent ergonomics, 80 against 67\n- Security \u0026 auth, 87 against 69\n- Maintenance \u0026 community, 87 against 73\n- Transparency \u0026 trust, 85 against 71\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where Kiro CLI loses 5 points for them\n\nWatch for: Public beta since 10 September 2026 behind the agents=v1 beta header, with no GA date\n\n\n## Why the edge\n\n### Security \u0026 auth: OpenAI Agents API +18\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- OpenAI Agents API (87): Project keys with restricted per-endpoint permissions, service accounts and workload identity, per the openai-api listing; we didn't confirm a key can be limited to /v1/agents (27 of 30). Automatic review for approvals, a sandbox network restricted to a host allowlist, vaults for secrets and a sandbox security guide (17 of 20). The agent reads web pages, MCP results and browser content; the sandbox security guide and approval flow are the mitigations, with no prompt-injection guide of its own found (8 of 15). Tracing, observability and usage per session and admin audit logs (15). SOC 2 Type 2, ISO 27001 family, Bugcrowd bounty and a disclosure policy, per the openai-api listing (20). Not ZDR-eligible and US residency only, recorded under transparency. 27 + 17 + 8 + 15 + 20 = 87.\n\n### Maintenance \u0026 community: OpenAI Agents API +14\n\n- Kiro CLI (73): 3.0.0 on 3 November 2026, after 2.37.1 on 31 October (30). 25 dated releases from 2.17.0 on 11 August to 3.0.0 on 3 November, plus five patches, read from the first three changelog pages back to 9 July (20). A public issue tracker with area labels and triage automation, 69 cli issues closed against 96 opened in the 30 days to 8 October, and a Discord server, per the 8 October check, not re-read on 3 November. We didn't establish how many replies come from staff (14). No SDK and no registry entry. The ACP server is kept current, with ACP sign-in added in 2.37.0 and a migration guide for clients moving to V3 (6). Closed source, so no CI or dependency health to read. The installer verifies checksums (3). 30+20+14+6+3 = 73.\n- OpenAI Agents API (87): Closed API. Last dated change 16 October 2026, Ultrafast mode and document skills (30). Four dated changelog entries in the 57 days since release, 10 September, 29 September, 9 October and 16 October (20). Changelog and help centre, as the openai-api listing reads them (12 of 15). Official SDKs carry beta.agents (15). SDK CI, per the openai-api listing (10). 30 + 20 + 12 + 15 + 10 = 87.\n\n### Transparency \u0026 trust: OpenAI Agents API +14\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- OpenAI Agents API (85): Closed service with clear terms, Apache-2.0 SDKs (15). Session state retained until deleted, deletable sessions and artifacts, not ZDR-eligible, US residency only, and the data-controls guide agrees; no retention period for artifacts after a sandbox expires (25 of 30). Dated deprecation notices with minimum periods for GA models; a beta API can change faster (15 of 20). Subprocessors and processing countries listed, per the openai-api listing (20). 15 + 25 + 15 + 20 = 75.\n\n### Agent ergonomics: OpenAI Agents API +13\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- OpenAI Agents API (80): Read as an API an agent drives. Context is compacted automatically, and session budgets and streamed events keep output sized (20 of 25). Sessions can be listed, continued and steered, events streamed or sent by webhook, artifacts fetched (15 of 20). Actionable error codes with recovery steps (20). No idempotency key; a documented check-then-retry procedure (10 of 20). One session call with defaults (medium sandbox, network enabled), SDKs in five languages (15). 20 + 15 + 20 + 10 + 15 = 80.\n\n### Payments \u0026 pricing: Kiro CLI +10\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- OpenAI Agents API (30): No machine payment protocol (0). Model, tool and container prices published without a login, and no fee for the API itself (20). The Free tier reading of the openai-api listing, half (10). Sign-up in a browser (0). 0 + 20 + 10 + 0 = 30.\n\n### Schema \u0026 documentation: OpenAI Agents API +9\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- OpenAI Agents API (88): The reference is linked from the overview and the SDKs carry beta.agents types; we didn't confirm /agents/sessions in OpenAI's public OpenAPI file, so 15 of 25. llms.txt with every Agents API page and Markdown twins (10). The overview, architecture page and the agents guide that compares the Agents API, Agents SDK and Responses API say when to use it (20). Typed configuration with enumerated container sizes, network modes and environment types (13 of 15). Examples in six languages and an errors page with codes per HTTP status, turn and session (15). Dated changelog entries and a versioned beta header (15). 15 + 10 + 20 + 13 + 15 + 15 = 88.\n\n## Score by category\n\n| Category | Weight | Kiro CLI | OpenAI Agents API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 57 | 60 | OpenAI Agents API +3 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 79 | 88 | OpenAI Agents API +9 |\n| Agent ergonomics | 13% (16.2 this run) | 67 | 80 | OpenAI Agents API +13 |\n| Security \u0026 auth | 14% (17.5 this run) | 69 | 87 | OpenAI Agents API +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 30 | Kiro CLI +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 73 | 87 | OpenAI Agents API +14 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 85 | OpenAI Agents API +14 |\n| Negative events | ≤15 | -5 | 0 | |\n| **Total** | | **59.8 · C** | **73.3 · BB** | |\n\n## Facts side by side\n\n| Fact | Kiro CLI | OpenAI Agents API |\n| --- | --- | --- |\n| Kind | Agent harness | HTTP API |\n| Vendor | Amazon Web Services | OpenAI |\n| Hosted endpoint | no (local only) | `https://api.openai.com/v1/agents/sessions` |\n| Transports | | https |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Pay per use |\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 | Proprietary hosted API under OpenAI's Services Agreement. The SDKs are Apache 2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-11-03 | 2026-10-16 |\n| Terms last updated | 2026-08-14 | couldn't be read |\n| Privacy policy last updated | 2026-05-18 | couldn't be read |\n| Customer content may train models | not found in the text | couldn't be read |\n| Terms restrict automated access | not found in the text | couldn't be read |\n| Terms restrict benchmarking | not found in the text | couldn't be read |\n| Terms or service can change without notice | not found in the text | couldn't be read |\n| Arbitration or class-action waiver | yes | couldn't be read |\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### OpenAI Agents API\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**OpenAI Agents API.** OpenAI's hosted agent runtime, the Codex harness behind one session call, with MCP, functions, web search, computer use, subagents and sandboxes on OpenAI or your own infrastructure. Documentation, errors and SDKs are thorough. It's still public beta, can't use Zero Data Retention and keeps data in the United States only.\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### OpenAI Agents API\n\n1. POST https://api.openai.com/v1/agents/sessions with a project key and the header OpenAI-Beta: agents=v1, or use client.beta.agents in the SDKs\n2. Before retrying, retrieve the session and turn and check which actions completed, since there's no idempotency key\n3. Set the sandbox network to restricted with an allowlist of up to 100 hosts when the agent doesn't need the open web\n4. Save files from /workspace/outputs before deleting a session; no retention period is stated for artifacts\n5. Don't send data that needs Zero Data Retention or non-US residency; the Agents API supports neither\n\n## Questions\n\n### Which is better for AI agents, Kiro CLI or OpenAI Agents API?\n\nOpenAI Agents API scores 73.3 (BB) on agent readiness against Kiro CLI's 59.8 (C), and leads in 6 of 7 scored categories. Kiro CLI leads on payments \u0026 pricing.\n\n### Can an agent call Kiro CLI and OpenAI Agents API without installing anything?\n\nNo hosted endpoint is listed for Kiro CLI. OpenAI Agents API has a hosted endpoint at https://api.openai.com/v1/agents/sessions.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/kiro-cli-vs-openai-agents-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/kiro-cli-vs-openai-agents-api.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"kiro-cli\", \"b\": \"openai-agents-api\"}`. From a terminal: `anchor compare kiro-cli openai-agents-api`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/kiro-cli.json and https://www.anchorterminal.com/api/v1/tools/openai-agents-api.json\n\n## Other comparisons with Kiro CLI or OpenAI Agents API\n\n- [Agent Zero vs Kiro CLI](https://www.anchorterminal.com/compare/agent-zero-vs-kiro-cli.md)\n- [Agent Zero vs OpenAI Agents API](https://www.anchorterminal.com/compare/agent-zero-vs-openai-agents-api.md)\n- [Aider vs Kiro CLI](https://www.anchorterminal.com/compare/aider-vs-kiro-cli.md)\n- [Aider vs OpenAI Agents API](https://www.anchorterminal.com/compare/aider-vs-openai-agents-api.md)\n- [Amp vs Kiro CLI](https://www.anchorterminal.com/compare/amp-vs-kiro-cli.md)\n- [Amp vs OpenAI Agents API](https://www.anchorterminal.com/compare/amp-vs-openai-agents-api.md)\n- [Antigravity CLI vs Kiro CLI](https://www.anchorterminal.com/compare/antigravity-cli-vs-kiro-cli.md)\n- [Antigravity CLI vs OpenAI Agents API](https://www.anchorterminal.com/compare/antigravity-cli-vs-openai-agents-api.md)\n- [Auggie CLI vs Kiro CLI](https://www.anchorterminal.com/compare/auggie-vs-kiro-cli.md)\n- [Auggie CLI vs OpenAI Agents API](https://www.anchorterminal.com/compare/auggie-vs-openai-agents-api.md)\n- [AXLR vs Kiro CLI](https://www.anchorterminal.com/compare/axlr-vs-kiro-cli.md)\n- [AXLR vs OpenAI Agents API](https://www.anchorterminal.com/compare/axlr-vs-openai-agents-api.md)\n- [Claude Code vs Kiro CLI](https://www.anchorterminal.com/compare/claude-code-vs-kiro-cli.md)\n- [Claude Code vs OpenAI Agents API](https://www.anchorterminal.com/compare/claude-code-vs-openai-agents-api.md)\n- [Cline vs Kiro CLI](https://www.anchorterminal.com/compare/cline-vs-kiro-cli.md)\n- [Cline vs OpenAI Agents API](https://www.anchorterminal.com/compare/cline-vs-openai-agents-api.md)\n- [Crush vs Kiro CLI](https://www.anchorterminal.com/compare/crush-vs-kiro-cli.md)\n- [Crush vs OpenAI Agents API](https://www.anchorterminal.com/compare/crush-vs-openai-agents-api.md)\n- [Cursor CLI vs Kiro CLI](https://www.anchorterminal.com/compare/cursor-cli-vs-kiro-cli.md)\n- [Cursor CLI vs OpenAI Agents API](https://www.anchorterminal.com/compare/cursor-cli-vs-openai-agents-api.md)\n- [DeepSeek Harness (dsh) vs Kiro CLI](https://www.anchorterminal.com/compare/deepseek-harness-vs-kiro-cli.md)\n- [DeepSeek Harness (dsh) vs OpenAI Agents API](https://www.anchorterminal.com/compare/deepseek-harness-vs-openai-agents-api.md)\n- [dsh-superagent (DeepSeek) vs Kiro CLI](https://www.anchorterminal.com/compare/deepseek-superagent-vs-kiro-cli.md)\n- [dsh-superagent (DeepSeek) vs OpenAI Agents API](https://www.anchorterminal.com/compare/deepseek-superagent-vs-openai-agents-api.md)\n- [Devin vs Kiro CLI](https://www.anchorterminal.com/compare/devin-vs-kiro-cli.md)\n- [Devin vs OpenAI Agents API](https://www.anchorterminal.com/compare/devin-vs-openai-agents-api.md)\n- [Droid CLI vs Kiro CLI](https://www.anchorterminal.com/compare/droid-cli-vs-kiro-cli.md)\n- [Droid CLI vs OpenAI Agents API](https://www.anchorterminal.com/compare/droid-cli-vs-openai-agents-api.md)\n- [Pi vs Kiro CLI](https://www.anchorterminal.com/compare/earendil-pi-vs-kiro-cli.md)\n- [Pi vs OpenAI Agents API](https://www.anchorterminal.com/compare/earendil-pi-vs-openai-agents-api.md)\n- [Gemini CLI vs Kiro CLI](https://www.anchorterminal.com/compare/gemini-cli-vs-kiro-cli.md)\n- [Gemini CLI vs OpenAI Agents API](https://www.anchorterminal.com/compare/gemini-cli-vs-openai-agents-api.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 OpenAI Agents API](https://www.anchorterminal.com/compare/github-copilot-cli-vs-openai-agents-api.md)\n- [goose vs Kiro CLI](https://www.anchorterminal.com/compare/goose-vs-kiro-cli.md)\n- [goose vs OpenAI Agents API](https://www.anchorterminal.com/compare/goose-vs-openai-agents-api.md)\n- [Harness² vs Kiro CLI](https://www.anchorterminal.com/compare/harness2-vs-kiro-cli.md)\n- [Harness² vs OpenAI Agents API](https://www.anchorterminal.com/compare/harness2-vs-openai-agents-api.md)\n- [HarnessRouter vs Kiro CLI](https://www.anchorterminal.com/compare/harnessrouter-vs-kiro-cli.md)\n- [HarnessRouter vs OpenAI Agents API](https://www.anchorterminal.com/compare/harnessrouter-vs-openai-agents-api.md)\n- [Jules vs Kiro CLI](https://www.anchorterminal.com/compare/jules-vs-kiro-cli.md)\n- [Jules vs OpenAI Agents API](https://www.anchorterminal.com/compare/jules-vs-openai-agents-api.md)\n- [Junie CLI vs Kiro CLI](https://www.anchorterminal.com/compare/junie-vs-kiro-cli.md)\n- [Junie CLI vs OpenAI Agents API](https://www.anchorterminal.com/compare/junie-vs-openai-agents-api.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 OpenAI Agents API](https://www.anchorterminal.com/compare/kilo-code-cli-vs-openai-agents-api.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 OpenAI Agents API](https://www.anchorterminal.com/compare/kimi-code-cli-vs-openai-agents-api.md)\n- [Kiro CLI vs mini-swe-agent](https://www.anchorterminal.com/compare/kiro-cli-vs-mini-swe-agent.md)\n- [Kiro CLI vs MiniMax Code](https://www.anchorterminal.com/compare/kiro-cli-vs-minimax-code.md)\n- [Kiro CLI vs Mistral Vibe CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-mistral-vibe-cli.md)\n- [Kiro CLI vs Muse Code](https://www.anchorterminal.com/compare/kiro-cli-vs-muse-code.md)\n- [Kiro CLI vs OpenAI Codex](https://www.anchorterminal.com/compare/kiro-cli-vs-openai-codex.md)\n- [Kiro CLI vs OpenCode](https://www.anchorterminal.com/compare/kiro-cli-vs-opencode.md)\n- [Kiro CLI vs OpenHands](https://www.anchorterminal.com/compare/kiro-cli-vs-openhands.md)\n- [Kiro CLI vs OpenMausBot](https://www.anchorterminal.com/compare/kiro-cli-vs-openmausbot.md)\n- [Kiro CLI vs Prime Agent](https://www.anchorterminal.com/compare/kiro-cli-vs-prime-agent.md)\n- [Kiro CLI vs Qoder CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-qoder-cli.md)\n- [Kiro CLI vs Qwen Code](https://www.anchorterminal.com/compare/kiro-cli-vs-qwen-code.md)\n- [Kiro CLI vs Mirror CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-reflection-mirror.md)\n- [Kiro CLI vs Rovo Dev CLI](https://www.anchorterminal.com/compare/kiro-cli-vs-rovo-dev-cli.md)\n- [Kiro CLI vs Unstoppable](https://www.anchorterminal.com/compare/kiro-cli-vs-unstoppable.md)\n- [Kiro CLI vs Vibe-Trading](https://www.anchorterminal.com/compare/kiro-cli-vs-vibe-trading.md)\n- [Kiro CLI vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/kiro-cli-vs-warp.md)\n- [mini-swe-agent vs OpenAI Agents API](https://www.anchorterminal.com/compare/mini-swe-agent-vs-openai-agents-api.md)\n- [MiniMax Code vs OpenAI Agents API](https://www.anchorterminal.com/compare/minimax-code-vs-openai-agents-api.md)\n- [Mistral Vibe CLI vs OpenAI Agents API](https://www.anchorterminal.com/compare/mistral-vibe-cli-vs-openai-agents-api.md)\n- [Muse Code vs OpenAI Agents API](https://www.anchorterminal.com/compare/muse-code-vs-openai-agents-api.md)\n- [OpenAI Agents API vs OpenAI Codex](https://www.anchorterminal.com/compare/openai-agents-api-vs-openai-codex.md)\n- [OpenAI Agents API vs OpenCode](https://www.anchorterminal.com/compare/openai-agents-api-vs-opencode.md)\n- [OpenAI Agents API vs OpenHands](https://www.anchorterminal.com/compare/openai-agents-api-vs-openhands.md)\n- [OpenAI Agents API vs OpenMausBot](https://www.anchorterminal.com/compare/openai-agents-api-vs-openmausbot.md)\n- [OpenAI Agents API vs Prime Agent](https://www.anchorterminal.com/compare/openai-agents-api-vs-prime-agent.md)\n- [OpenAI Agents API vs Qoder CLI](https://www.anchorterminal.com/compare/openai-agents-api-vs-qoder-cli.md)\n- [OpenAI Agents API vs Qwen Code](https://www.anchorterminal.com/compare/openai-agents-api-vs-qwen-code.md)\n- [OpenAI Agents API vs Mirror CLI](https://www.anchorterminal.com/compare/openai-agents-api-vs-reflection-mirror.md)\n- [OpenAI Agents API vs Rovo Dev CLI](https://www.anchorterminal.com/compare/openai-agents-api-vs-rovo-dev-cli.md)\n- [OpenAI Agents API vs Unstoppable](https://www.anchorterminal.com/compare/openai-agents-api-vs-unstoppable.md)\n- [OpenAI Agents API vs Vibe-Trading](https://www.anchorterminal.com/compare/openai-agents-api-vs-vibe-trading.md)\n- [OpenAI Agents API vs Warp (Warp Agent CLI and the Oz Agent API)](https://www.anchorterminal.com/compare/openai-agents-api-vs-warp.md)\n- [Clawboo vs Kiro CLI](https://www.anchorterminal.com/compare/clawboo-vs-kiro-cli.md)\n- [CLI Manager vs Kiro CLI](https://www.anchorterminal.com/compare/cli-manager-vs-kiro-cli.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-06", "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 OpenAI Agents API", "url": "" } ], "description": "OpenAI Agents scores 73.3 (BB) to Kiro CLI's 59.8 (C) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Kiro CLI C 59.8", "OpenAI Agents API BB 73.3", "scores" ], "h1": "Kiro CLI vs OpenAI Agents API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/kiro-cli-vs-openai-agents-api", "published": "2026-10-01", "section": "tools", "title": "Kiro CLI vs OpenAI Agents for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-06", "url": "https://www.anchorterminal.com/compare/kiro-cli-vs-openai-agents-api" }, "tokens": { "markdown": 6600, "slim": 3180 }, "version": 1 }