floatboat
Open navigation menu

Moonshot AI: Kimi and Agent Tools

Explore Moonshot AI’s public coding-agent work through Kimi Code CLI. Understand the current project, the retired Python CLI, and how model services, editor interfaces, and reusable extensions fit together.

About Moonshot AI

Moonshot AI, also known as 月之暗面, develops the Kimi ecosystem and publishes tools for model-driven work. Kimi Code CLI is a representative public coding-agent project, giving the organization a software-tooling role beyond providing a model endpoint.

The maintained Kimi Code CLI combines a terminal application, development tools, plugins, subagents, and ACP editor integration. These are complementary parts of a coding workflow, with the editor, runtime, and model each retaining their own responsibilities.

The legacy Python kimi-cli repository is archived and points to kimi-code. The two addresses represent a legacy version and its maintained successor. MIT licensing for the current source is also separate from Kimi Code subscriptions and Moonshot API access.

Moonshot AI Projects

Explore the project as a reference for designing your own agent workflows, with attention to task structure, extensions, and execution boundaries.

Related Agent Publishers

Explore other teams developing agent runtimes, coding tools, and reusable working environments.

Moonshot AI FAQ

Is Moonshot AI the same organization as 月之暗面?
Moonshot AI is the organization’s English name used for its public developer presence. The Kimi Code CLI repository is published under the official MoonshotAI GitHub organization.
Which Kimi coding project is currently maintained?
MoonshotAI/kimi-code is the maintained Kimi Code CLI. The legacy Python kimi-cli repository is archived and directs users to its successor.
Why not count both Kimi CLI repositories as current projects?
The old repository is archived and no longer maintained. Treating both as active recommendations would hide the migration and lead readers toward obsolete instructions.
Does the coding application require every model to be from Moonshot?
The current CLI documentation allows compatible providers. Compatibility and access are still specific to the selected service; the publisher identity does not settle every provider feature.
Are editor support and the coding runtime the same product layer?
No. ACP-compatible editors provide an interface to a CLI session. The runtime, editor integration, and model service should be assessed separately when planning a workflow.
Does the CLI license grant a Kimi account entitlement?
No. The MIT source license does not determine subscription access, API usage, quotas, or provider billing. Those belong to the account and service terms.

Study Kimi Code CLI Workflow Design

Read the project guide to identify useful mechanisms and plan a small workflow experiment.

View Kimi Code CLI