A source-backed comparison of three coding-agent workflows across local repository work, supported surfaces, extensibility, provider choice, open-source licensing and access paths.
Quick answers
This page compares Kimi Code, Claude Code, and Codex as separate product choices. The table focuses on workflow fit rather than assuming one option is the universal baseline.
Choose Kimi Code when you want an MIT-licensed terminal agent centered on Kimi models, compatible providers, ACP and an open plugin stack. Choose Claude Code when Anthropic's broad terminal, IDE, desktop and web workflow is the priority. Choose Codex when you want OpenAI's Apache-2.0 CLI together with Codex desktop, IDE, cloud and automation surfaces.
Official documentation and public repositories were checked on August 26, 2026. This comparison evaluates product shape and documented workflow capabilities; it does not claim a universal coding-quality winner or use unverified benchmark scores.
Where the agent runs and how it connects to local or remote development work.
Documented support for MCP, plugins or skills, hooks, subagents, SDKs and editor protocols.
Authentication, provider choice, licensing, permissions and the surfaces included with each service.
Open terminal agent with Kimi models
Kimi CodeIts MIT-licensed CLI documents Kimi OAuth, Moonshot API keys, compatible providers, video input, MCP, plugins, hooks, subagents and ACP.
Anthropic-native multi-surface workflow
Claude Code
Official documentation covers terminal, VS Code, JetBrains, desktop and web, plus MCP, skills, hooks, parallel agents and the Agent SDK.
OpenAI coding workflow and automation
Codex
Official documentation connects the Apache-2.0 CLI with IDE, desktop, cloud, review, scripting, CI, skills, plugins, MCP and SDK workflows.
| Criterion | Kimi Code | Claude Code | Codex | Note |
|---|---|---|---|---|
| Local repository work | Terminal agent that reads and edits files, runs shell commands, searches files and uses tool feedback. | Terminal and IDE agent that reads codebases, edits files, runs commands and integrates with development tools. | Local CLI for inspecting and editing repositories, running commands, reviewing changes and scripting repeatable tasks. | All three support the core local coding loop; permission defaults and tool policies should be evaluated separately. |
| Supported surfaces | Terminal TUI plus ACP integration for Zed, JetBrains and compatible clients. | Terminal, VS Code, JetBrains, desktop app and web, with remote and cloud handoff workflows. | CLI, IDE extension, desktop app and cloud surfaces, with non-interactive and CI paths. | Choose based on where reviews, approvals and long-running tasks need to happen. |
| Extensibility | Conversational MCP configuration, plugins with trust labels, lifecycle hooks, isolated subagents and ACP. | MCP, CLAUDE.md, skills, hooks, parallel agents, background agents and Agent SDK. | AGENTS.md, skills, plugins, MCP, subagents, hooks, SDK, app server and non-interactive execution. | Extension ecosystems are not interchangeable; audit every plugin, MCP server and hook before team rollout. |
| Models and providers | Works with Kimi models out of the box and documents compatible provider configuration. | Centered on Claude; official terminal and IDE documentation also notes supported third-party providers. | Centered on OpenAI models through ChatGPT sign-in or supported API configuration. | Model availability, context, rate limits and routing can vary by account and change independently from the agent client. |
| Source license | Public CLI repository under the MIT License. | The official product documentation does not present Claude Code itself as an open-source CLI. | Public CLI repository under the Apache-2.0 License. | A client license does not grant rights to hosted models or remove provider service terms. |
| Access and pricing | Free open-source CLI; hosted use can involve Kimi Code membership, Moonshot API billing or another configured provider. | Most surfaces require a Claude subscription or Anthropic Console account; supported provider routes vary by surface. | Supports ChatGPT sign-in and documented API-key setup; included usage depends on the current ChatGPT plan or API billing. | Verify the current plan page immediately before purchase; client installation price and model usage price are different questions. |