logo

MoonshotAI/kimi-cli

[Archived] Legacy Python Kimi CLI, no longer maintained. Please use Kimi Code CLI: https://github.com/MoonshotAI/kimi-code

View on GitHub ↗Jump to charts ↓Open shareable report →

MoonshotAI/kimi-cli has 11k+ stars and 1k+ forks on GitHub, is written in Python, and was last pushed on Sep 22, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 15 minutes ago
Type:CLI ToolCategory(s):AI Coding AgentsAgent Frameworks & SDKsAI Agents & LLM Apps
Added to GitGenius on January 31st, 2026
Created on October 15th, 2025
Open Issues & Pull Requests: 794 (+0)
GitHub issues: Enabled
Number of forks: 1,335
Total Stargazers: 11,416 (+0)
Total Subscribers: 60 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.1 hours
Mean response time: 6.7 days
90th percentile: 20.5 days
Tracked items: 641

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

12 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 81% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 54% of issues opened in the past year have been closed. Three people close 55% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 490
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 22 days
Stale 30+ days: 484
Stale 90+ days: 402

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (456)
  • enhancement (296)
  • Web (10)
  • VS Code (6)
  • dependencies (2)
  • good first issue (1)
  • wontfix (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

Kimi CLI is a terminal-based AI agent that helps developers complete software development tasks and terminal operations.

The tool addresses the need for an AI assistant integrated directly into the development workflow. It works by running in the terminal where it can read and edit code, execute shell commands, search and fetch web pages, and autonomously plan and adjust actions during execution. Users can switch between standard agent mode and a dedicated shell command mode by pressing Ctrl-X, allowing direct shell command execution without leaving the tool.

Developers should adopt this tool if they want an AI agent deeply integrated with their terminal environment and code editor. It suits projects where developers spend significant time in the terminal and want AI assistance without context switching. The tool offers integration with Visual Studio Code through an extension, supports the Agent Client Protocol for compatibility with ACP-enabled editors like Zed and JetBrains IDEs, and can be integrated with Zsh to enhance shell capabilities. It also supports MCP (Model Context Protocol) tools for extended functionality. However, the README notes that built-in shell commands like cd are not yet supported. The project is evolving into Kimi Code CLI as its next-generation successor, with existing installations able to migrate automatically.

Almost all open issues are raised by outside users rather than the core team, indicating a substantial base of adopters reporting real-world use. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker is dominated by bug reports, enhancement requests, and Web-related issues.