Kilo Code is an open-source, model-agnostic AI coding agent platform available for VS Code, JetBrains IDEs, and the terminal (Kilo CLI). It positions itself as a superset of both Cline and Roo Code, combining Cline's beginner-friendly approval-gating with Roo Code's advanced features like custom modes and persistent context management.
Founded in 2025 by Scott Breitenother (CEO, ex-Brooklyn Data) and backed by GitLab co-founder Sid Sijbrandij. Licensed under Apache 2.0 with zero-markup pay-as-you-go model routing. Raised $8M seed (Dec 2025) from Cota Capital, General Catalyst, and others. The platform is #1 on OpenRouter by token volume, processing over 6 trillion tokens per month.
Best fit: Developers who want model flexibility (500+ models via OpenRouter, BYOK, or local models), teams transitioning from Cline or Roo Code, and budget-conscious developers who want agentic coding without subscription commitments. Not ideal for enterprises requiring SOC 2 compliance or centralized admin controls today.
Adoption & Proof Points
- GitHub: 15.1K stars, 1.9K forks (Feb 2026). Active contributor community.
- Installs: 420K+ on VS Code Marketplace. 750K+ total user accounts across platforms.
- Usage: #1 app on OpenRouter by token volume. 6.1 trillion tokens/month processed.
- Funding: $8M seed (Dec 2025) led by Cota Capital with Breakers, General Catalyst, Quiet Capital, Tokyo Black.
- Team: ~32-34 employees distributed globally. Co-founders: Scott Breitenother (CEO) and Sid Sijbrandij (GitLab co-founder).
- Community: Discord ~11,700 members. Product Hunt #1 Product of the Day, #1 of the Week (Jan 2026).
- Strategic interest: GitLab holds right of first refusal on acquisition proposals until August 2026.
Recommended Use Cases
- Multi-file feature development using Orchestrator mode to delegate Architect, Code, and Debug subtasks
- Budget-conscious AI-assisted development via free or low-cost models on OpenRouter
- Codebase Q&A and developer onboarding using Ask mode with Memory Bank context
- Chat-to-PR workflows via Kilo for Slack, turning Slack threads into GitHub pull requests
- CI/CD pipeline automation using Kilo CLI's headless autonomous mode
- Teams wanting model provider flexibility without vendor lock-in to a single LLM
Risks & Limitations
- No formal compliance certifications (SOC 2, ISO 27001). Enterprise proxy gateway is in early access, not GA.
- No SSO integration, centralized admin console, or team-wide spend controls documented as of Feb 2026.
- Very young company (founded 2025, seed-funded Dec 2025). Rapid product evolution may introduce breaking changes.
- Code context transmitted to third-party LLM providers whose retention policies vary. No formal DPA from Kilo.
- Configuration complexity: Memory Bank, MCP servers, and custom modes require meaningful setup investment.
- Autocomplete (Kilo Complete) is experimental; model is not yet configurable.
- GitLab acquisition right of first refusal (until Aug 2026) introduces long-term independence uncertainty.
- Crowded market: Competing directly with Cline (5M+ installs), Roo Code, Cursor, Windsurf, Claude Code, and GitHub Copilot.
Capabilities & Integration
Multi-mode architecture: Code mode (multi-file generation), Architect mode (read-only planning), Debug mode (error diagnosis), Ask mode (codebase Q&A), and Orchestrator mode (subtask delegation across modes). Custom modes configurable via YAML files.
Model support: 500+ models via OpenRouter, direct API keys (Anthropic, OpenAI, Google, AWS Bedrock, Azure), and local models via Ollama. No hidden model selection—users always know which model is active. Kilo Complete (autocomplete) powered by Gemini 2.5 Flash.
MCP integration: Full Model Context Protocol support with STDIO (local) and SSE (remote) transport. Community-driven MCP marketplace at github.com/Kilo-Org/kilo-marketplace. Extends capabilities to databases, APIs, and web scraping.
Platform surface: VS Code (420K+ installs), JetBrains IDEs (official plugin), Kilo CLI (v1.0 Feb 2026, supports autonomous CI/CD mode), and Kilo for Slack (mention @Kilo in threads to generate PRs from chat). Browser automation via Puppeteer with user approval.
Memory Bank: Persistent project-level context stored as structured Markdown in .kilocode/rules/memory-bank/. Remembers architectural decisions, conventions, and preferences across sessions and platforms.