Marius
452ab52d47
* feat: enable reasoning for Claude models via Kilo Gateway Enable extended thinking/reasoning support for Claude models when using Kilo Gateway (OpenRouter-based). This includes: - Add Kilo Gateway to OpenRouter SDK key mapping - Skip toolCallId normalization for OpenRouter/Kilo to preserve thinking blocks - Strip thinking/reasoning blocks from messages before sending to avoid Anthropic API signature validation errors (blocks must be unchanged) - Skip caching for OpenRouter/Kilo to avoid modifying thinking blocks - Add Claude-specific reasoning effort variants for Kilo Gateway - Enable default medium reasoning effort for Claude via Kilo Gateway - Add proper smallOptions handling for Claude vs other models The key insight is that Anthropic's API requires thinking blocks to be EXACTLY unchanged with valid signatures. Since our storage reconstructs messages, we strip thinking blocks (already shown to user) rather than risk signature validation failures. * fix: drop empty messages after stripping thinking blocks
The open source AI coding agent.
Installation
# npm
npm install -g @kilocode/cli
# Or run directly with npx
npx @kilocode/cli
Then run kilo in any project directory to start.
Agents
Kilo CLI includes two built-in agents you can switch between using the Tab key:
- build - Default, full access agent for development work
- plan - Read-only agent for analysis and code exploration
- Denies file edits by default
- Asks permission before running bash commands
- Ideal for exploring unfamiliar codebases or planning changes
Also included is a general subagent for complex searches and multi-step tasks.
This is used internally and can be invoked using @general in messages.
Autonomous Mode (CI/CD)
Use the --auto flag with kilo run to enable fully autonomous operation without user interaction. This is ideal for CI/CD pipelines and automated workflows:
kilo run --auto "run tests and fix any failures"
Important: The --auto flag disables all permission prompts and allows the agent to execute any action without confirmation. Only use this in trusted environments like CI/CD pipelines.
Migrating from Kilo Code Extension
If you're coming from the Kilo Code VS Code extension, your configurations are automatically migrated:
| Kilo Code Feature | Kilo CLI Equivalent |
|---|---|
| Custom modes | Converted to agents |
Rules (.kilocoderules, .kilocode/rules/) |
Added to instructions array |
Skills (.kilocode/skills/) |
Auto-discovered alongside .opencode/skill/ |
Workflows (.kilocode/workflows/) |
Converted to commands |
| MCP servers | Migrated to mcp config |
Default mode mappings:
code→buildagentarchitect→planagent
For detailed migration information, see:
Documentation
For more info on how to configure Kilo CLI, head over to our docs.
Contributing
If you're interested in contributing, please read our contributing docs before submitting a pull request.
FAQ
Where did Kilo CLI come from?
Kilo CLI is a fork of OpenCode, enhanced to work within the Kilo agentic engineering platform.