Moonshot AI Releases Kimi Code CLI Terminal Agent with Agent Client Protocol Support
Moonshot AI introduced Kimi Code CLI, a single-binary terminal coding agent that runs without Node.js dependencies. It supports Agent Client Protocol for IDE integration in Zed and JetBrains, conversational Model Context Protocol setup via /mcp-config, and subagents for parallel execution.
Impact: Medium
Why it matters
Engineers get a fast terminal coding agent that plugs directly into existing IDEs like Zed while managing Model Context Protocol servers conversationally.
TL;DR
- 01Install Kimi Code CLI via single binary without Node.js setup
- 02Manage MCP servers conversationally inside chat using /mcp-config
- 03Connect terminal sessions to Zed or JetBrains using Agent Client Protocol via `kimi acp`
Key facts
- Distribution
- Single binary (no Node.js)
- Protocol
- Agent Client Protocol (ACP)
- UI Engine
- pi-tui
Terminal Agent Built for Speed
Kimi Code CLI ships as a single-binary distribution requiring no Node.js runtime. Built on pi-tui, the terminal user interface launches in milliseconds. Installation is executed via a simple shell script (curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash). On first launch, users log in using OAuth or a Moonshot AI API key.
Subagents and Lifecycle Hooks
The agent introduces built-in subagents (coder, explore, and plan) that handle isolated background tasks to keep main context windows clean. Custom lifecycle hooks allow developers to trigger local commands, audit tool executions, or block unsafe operations.
Conversational MCP and IDE Integration
Developers can configure Model Context Protocol servers directly inside chat using the /mcp-config command. Additionally, Kimi Code CLI supports the Agent Client Protocol (kimi acp), letting Zed and JetBrains drive terminal agent sessions over standard I/O.
Try it in 2 minutes
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bashbash
✓ When to use
- When you need a fast terminal coding agent with zero runtime setup
- When orchestrating MCP servers alongside Zed or JetBrains IDEs
✕ When NOT to use
- When working in GUI-only environments without terminal access
What to do today
- Run install script to test Kimi Code CLI locally
- Configure MCP integrations using /mcp-config inside the TUI
- Enable ACP integration in Zed settings
Sources