Kimi Code CLI vs OpenAI Agents API

Kimi Code CLI 45

Harness reading of the framework checklist. 30 for credentials and what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. OAuth tokens sit in 0600 files and shell keys aren't read unless named. Telemetry is on by default and, in the 2.2.0 package read on 18 October, sends events with a device ID, session ID and model name to telemetry-logs.kimi.com. Auto-update is on by default (14). Interactive sessions ask before edits and commands, and a dangerous-command guard covers rm -rf and similar, but kimi -p runs under Never Ask, where everything is approved and the guard is off, with only static deny rules left. No sandbox found, and hooks fail open (7). The MCP page warns about untrusted servers and project .kimi-code/mcp.json entries, and since 2.1.0 project config waits for workspace trust, but no prompt-injection guidance was found for fetched web pages (6). Sessions on disk, kimi export, the kimi vis session visualiser, a diagnostic log and hooks for auditing (11). SECURITY.md names private GitHub advisories and an email, supports only the latest version and gives no response time. No security.txt was found on kimi.com, kimi.ai or moonshot.ai, and OSV, read again on 2 November 2026, lists no advisories for the package, though 2.1.0 shipped security fixes (7).

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.

Kimi Code CLI 60

Self-hosted rule. No payment protocol (0). The CLI is free under MIT with nothing to buy (20). No card or account is needed for the software, and any listed provider's key works (20). An agent can install it from npm and run it with KIMI_MODEL_* variables and no sign-up, given a model key (20). The Kimi Code subscription and Kimi Platform API usage are separate purchases.

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.

Kimi Code CLI 62

MIT (30). The docs have no privacy page for the CLI. The Kimi terms (effective 13 August 2026, NOVASCENT PRIVATE LIMITED, Singapore) let Moonshot use content to train its services unless the user opts out by email, prospectively only, and the Kimi privacy policy says content is used for training. The Kimi Platform privacy policy keeps inputs while the account is active. Neither says which applies to CLI sessions (12). The kimi server tree prints a deprecation notice until the next major version, a table names each deprecated config key and the version that replaced it, and the Python Kimi CLI was archived with a migration guide, though its notice gives no date for when old installations stop working (13). Telemetry is documented as on, with a config key and an environment variable to turn it off, but what it collects isn't listed, and print mode ignored the opt-out until 0.41.0 (9).

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.

Kimi Code CLI 72

2.4.1 on 30 October 2026 (30). 30 stable tags from 0.32.0 on 4 August to 2.4.1 on 30 October, plus canary builds since 29 October (20). The 18 October counts from shields.io badges are struck. The clone shows the pace directly, 95 commits from 13 authors between 18 October and 2 November and pull requests numbered past #4600, with the changelog crediting outside contributors in each release. Issue reply times couldn't be read (11). No published SDK. A TypeScript SDK sits in the repository (@moonshot-ai/kimi-code-sdk 0.22.0) marked private, the ACP server and REST API ship inside the CLI, and Homebrew core is current at 2.4.1 (5). CI with a frozen lockfile, lint and a dependency check (sherif), canary and release workflows, no Dependabot or Renovate file, and the pass state unchecked (6). 30 + 20 + 11 + 5 + 6 = 72.

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.

Kimi Code CLI 71

Framework reading, adapted to a harness driven by a pipeline. Global tools.enabled and tools.disabled lists, per-agent tool lists, deferred MCP tool loading and a read-only Plan mode (20). stream-json output and a step limit per turn by environment variable, but steps are unlimited by default and there's no wall-time or cost limit for the main turn (13). The server API returns coded envelopes and ACP returns standard JSON-RPC errors, but print mode documents no exit codes outside goal runs (12). Retries only on transient failures and never on an exhausted quota, with --continue, --session, fork, undo and ACP session/load (16). kimi -p needs one argument, with ACP and the REST API as programmatic surfaces but no SDK package in any language (10).

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.

Kimi Code CLI 68

Local-package reading. An install script that verifies a checksum, npm @moonshot-ai/kimi-code with Node 22.19.0 or newer stated, and Homebrew core at 2.4.1, for macOS, Linux and Windows (20). A public CI workflow runs the build, a smoke test, sharded tests on Linux, tests on Windows, lint and typecheck. GitHub's pages answer 403 in this session, so whether it passes on main wasn't checked (15). The 18 October issue and pull-request counts came from shields.io badges, a third-party copy of GitHub data this run bars, so they are struck. The clone shows 95 commits from 13 authors since 18 October and a changelog that credits merged pull requests up to #4553 in 2.4.1, but which open issues are crashes or regressions, and how fast they're answered, couldn't be read (8). Changesets changelog with Major, Minor and Patch headings and no breaking-change label since 0.28.0. 2.2.0 made executor = "kaos" configs fail validation, 2.3.0 stopped bare-name plugin skill calls and 2.3.2, a patch, removed swarms from kimi -p and ACP (10). 2.4.1, past 1.0 (15). 20 + 15 + 8 + 10 + 15 = 68.

OpenAI Agents API 60

Read as a hosted API. status.openai.com has an Agents component under APIs (20). Since release on 10 September (57 days, not 90), the feed names the Agents API in a degraded-performance incident on 14 September, the elevated errors across ChatGPT, Codex and the API on 29 September (the openai-api listing reads that one as a major, 17:52 to 23:14 UTC), computer use issues and degraded workspace agents on 6 and 7 October, degraded performance across the APIs for 22 minutes on 21 October, and overbilling for hosted containers on 19 September. One major, the rest minor (10). Rate limits come from the shared guide, published per tier and model with headers, and the errors page adds a Files API allowance on session creation (15). 429 and 503 guidance with Retry-After, capped backoff and a check-then-retry procedure for turns (15). The Scale Tier SLA in the openai-api listing isn't shown to cover a beta API (0). Public beta behind the agents=v1 header (0). 20 + 10 + 15 + 15 + 0 + 0 = 60.