Kilo Code

Kilo Code, also referred to simply as Kilo, is an open-source AI coding agent published by Kilo Code, Inc., which Anaconda acquired in July 2026. It runs as a Visual Studio Code extension, as a native JetBrains plugin, as a terminal program, and as a hosted cloud agent, and it is distributed under the MIT License from the repository Kilo-Org/kilocode on GitHub ^[1][2][32]. The project describes itself as "the all-in-one agentic engineering platform" and advertises access to more than 500 models at provider list prices with no markup ^[1][2].

The project's lineage runs through two distinct codebases. It began in March 2025 as a fork of Roo Code, which was itself a fork of Cline, and marketed itself as a feature superset of both ^[3][4][8]. In February 2026 Kilo replaced that codebase with a new monorepo built on opencode's server core, moved the Roo-derived source to an archived kilocode-legacy repository, and ended support for the old extensions on 31 July 2026 ^{[5][6][7][9][10]}.

As of 1 October 2026 the GitHub repository had 27,460 stars and 3,219 forks ^[2], the Visual Studio Marketplace listing reported 1,587,885 installs ^[34], and OpenRouter's app directory credited the Kilo Code integration with 17.3 trillion cumulative tokens routed through its API, placing it second by daily volume among all tracked applications ^[43].

Lineage and history

Fork of Roo Code (2025)

The Kilo-Org GitHub organisation was created on 4 March 2025, the Visual Studio Marketplace extension kilocode.Kilo-Code was first published on 7 March 2025, and the Kilo-Org/kilocode repository was created on 10 March 2025 ^[2][34]. An Internet Archive capture of the repository page from 26 March 2025 shows GitHub's fork banner reading "forked from RooVetGit/Roo-Code" and a project description of "Kilo Code (forked from Roo Code) gives you a whole dev team of AI agents in your code editor" ^[3]. The working tree at that point still carried Cline-era and Roo-era artefacts including cline_docs, .clinerules and .rooignore ^[3].

By May 2025 the repository's description had changed to "Open Source AI coding assistant for planning, building, and fixing code. We're a superset of Roo, Cline, and our own features", and the README stated plainly: "Kilo Code is a direct fork from Roo Code, but also includes the following features from Cline (and more)", listing an MCP server marketplace, system notifications and easier model connection as the Cline-derived additions ^[4]. That snapshot also records the project at 257 GitHub stars and an Apache-2.0 licence ^[4].

Kilo has restated the chain itself. A May 2026 retrospective by Brendan O'Leary says the team "formed in a week, forked Roo Code, which itself came from Cline", and that the project "did not start from a blank repo. It came through Cline and Roo, then later rebuilt large parts of the stack around OpenCode" ^[8]. An April 2026 post put it more briefly: "Kilo started as a fork of Roo. We've been contributing back upstream since our inception" ^[7].

Rebuild on the opencode core (2026)

Kilo first published the @kilocode/cli npm package on 13 October 2025 ^[37]. In late January and early February 2026 it shipped Kilo CLI 1.0, described by VentureBeat as "a complete rebuild of its command-line tool" supporting more than 500 models and built on "an MIT-licensed, open-source foundation" ^[40]. FastForward, which covered the release a day earlier, reported that Kilo had "rebuilt its original CLI into a single, model-agnostic tool" and planned to make its backend infrastructure repositories source-available that week ^[39].

That foundation was opencode, the terminal coding agent maintained by Anomaly Innovations. The current README answers the question "Where did Kilo CLI come from?" with: "Kilo CLI is a fork of OpenCode, enhanced to work within the Kilo agentic engineering platform" ^[1]. The repository's MIT licence file carries two copyright lines, "Copyright (c) 2026 Kilo Code" and "Copyright (c) 2025 opencode" ^[32], the tree contains an .opencode-version marker and a packages/opencode/ directory, and the contributing guide instructs developers editing shared packages/opencode/ files to mark Kilo-specific edits with // kilocode_change comments so they stay distinguishable from upstream code ^[2][33].

The repository switch happened in February 2026. A second public repository, Kilo-Org/kilo, was created on 26 January 2026 under the MIT licence; it is now archived and its README reads only "This repo has been moved to https://github.com/Kilo-Org/kilocode", with its last push on 24 February 2026 ^[6]. Kilo-Org/kilocode-legacy was created on 22 February 2026 to hold the Roo-derived extension and its Apache-2.0 licence, and the first release tags of the new kilocode monorepo were published on 23 February 2026 ^[2][5]. GitHub no longer records Kilo-Org/kilocode as a fork of any repository ^[2].

The user-facing migration followed over the next five months. A rebuilt VS Code extension entered pre-release on 10 March 2026 and reached general availability on 2 April 2026, at which point Kilo said the previous extension had "served over 2.2 million developers" but that every surface, including JetBrains and Cloud Agents, had still been "running VS Code internals, whether it needed them or not" ^[9][10]. A rewritten JetBrains plugin, written in Kotlin with a Swing user interface rather than an embedded webview, reached general availability on 9 July 2026 after roughly two months and 50-plus pull requests of work ^[11]. The legacy repository's README records that the legacy VS Code extension and JetBrains plugin "reached end of life on July 31, 2026" and that Kilo would no longer ship updates, bug fixes or security patches for them ^[5].

Timeline

Where it runs

Kilo ships one agent across several surfaces that share the same portable server core ^[1][10]:

A separate hosted product, Gas Town, orchestrates fleets of agents against a repository. Kilo's documentation describes it as "an autonomous agent orchestration platform that manages teams of AI agents working on your codebase", built on the open Gastown orchestration protocol, with coding agents ("polecats"), a review agent ("refinery") and a conversational coordinator ("the mayor") ^[24].

Agents, subagents and modes

The Roo-derived extension used named "modes": Code, Architect, Debug, Ask and Orchestrator, each with its own system prompt and tool permissions, plus user-defined custom modes ^[5][39]. The rebuilt product renames these "agents" and ships four built-in primary agents ^[13]:

Orchestrator survives only as a deprecated agent "scheduled for removal". The documentation explains that agents with full tool access (code, plan and debug) now delegate to subagents directly through a task tool, so a dedicated orchestrator is no longer needed; read-only agents such as ask cannot delegate ^[13][14]. Two subagents are built in: general, a full-access agent for multi-step work, and explore, a read-only agent for codebase search ^[15]. Subagents run with separate conversation history but share the parent's project directory or worktree, so they do not isolate file edits, and a parent can launch several concurrently or run one in the background and collect its result later ^[14][15]. Custom subagents are defined in a kilo.jsonc config file or as Markdown agent files, and each agent carries a mode of primary, subagent or all ^[15].

A feature called Kilo Swarm lets a main session and its task descendants exchange findings on a shared board; it is on by default and is disabled in settings or by setting shared_agent_board to false ^[14]. Kilo's own September 2026 write-up on Swarm reported "a 39% cost cut on the task it's built for" and described the cost effect elsewhere as inconclusive ^[30].

Alongside the agent loop, the extensions provide inline autocomplete with ghost text, self-checking, terminal and browser control, code actions, prompt enhancement, commit-message generation, voice transcription, checkpoints (renamed snapshots in the rebuilt extension) and an Agent Manager that runs parallel sessions in separate git worktrees with inline, line-level diff review ^[1][9][10].

An --auto flag on kilo run auto-approves permission prompts "unless a rule explicitly denies the action", intended for CI and CD pipelines; the README warns it should only be used in trusted environments ^[1].

Context and memory

Context handling is split across several documented features: codebase indexing, context condensing with a configurable auto-compaction threshold, a .kilocodeignore file, AGENTS.md project instructions, custom rules and workflows ^[16][26].

Kilo Memory, announced on 22 July 2026, stores project-scoped notes that persist across sessions ^[12][16]. It is disabled by default, must be enabled per project, and holds only project memory rather than user-level memory ^[16]. Memory lives in three Markdown source files (project.md for facts and constraints, environment.md for commands and tooling, corrections.md for corrections to earlier memory) plus session digests, in a per-project folder under Kilo's global data directory keyed by a hash of the repository path ^[12][16]. Linked git worktrees share one project memory ^[16]. Auto-save is on once memory is enabled, sends best-effort-redacted turn context to the configured model provider, only adds or updates entries rather than deleting them, discards content matching common secret patterns, and is throttled ^[16].

Kilo Memory replaced an earlier "Memory Bank", a set of rule files under .kilo/rules/memory-bank/ that is now deprecated in favour of AGENTS.md ^[16]. The Memory Bank was the feature VentureBeat described in February 2026 as Kilo's answer to "AI amnesia" ^[40].

Extensibility

Kilo is an MCP client. Its documentation presents the Model Context Protocol as the standard mechanism for adding tools, exposes both STDIO and SSE transports, and applies the same allow / ask / deny permission model to MCP tools as to built-in ones ^[19]. The company's own FAQ calls Kilo "a first-class MCP client" with a built-in marketplace for one-click installs ^[28].

The project also implements Agent Skills, the open SKILL.md format. Skill metadata is scanned at start-up and injected into the system prompt, and the full instruction file is loaded only when the model decides a skill applies; there is no keyword matching or semantic search ^[17]. Skills can be generic or scoped to a particular mode, and user-level skills installed at ~/.agents/skills/<name>/SKILL.md are discovered without extra configuration ^[17].

The Kilo Marketplace distributes four kinds of item, each installable at project scope (under the repository's .kilo/ directory, so it can be committed and shared) or global scope ^[18]:

Model access and the Kilo Gateway

Kilo is model-agnostic by design. CEO Scott Breitenother told FastForward: "There are just so many amazing models coming out, and we see a lot of folks restricting themselves to a handful of models. We believe in model freedom" ^[39]. Users can run free models, bring their own provider keys, run local models through Ollama or LM Studio, or buy pay-as-you-go credits through Kilo's hosted gateway ^[27].

The Kilo AI Gateway is an OpenAI-compatible endpoint at https://api.kilo.ai/api/gateway that fronts hundreds of models with streaming, per-request cost and token tracking at microdollar precision, encrypted-at-rest bring-your-own-key storage, organisation model allow lists, provider restrictions and per-user daily spending limits ^[20]. The pricing page describes it as "500+ models across 60+ providers" charged at "exact provider rates with no markup" ^[27]. VentureBeat reported the same pass-through arrangement in February 2026: "$1 of Kilo credits is equivalent to $1 of provider costs" ^[40].

Auto Model is a router layered on top. It offers three tiers, kilo-auto/frontier for maximum capability, kilo-auto/efficient for lowest cost per task, and kilo-auto/free for the best available free models, and selects an underlying model per request ^[21][28].

Pricing

Kilo separates platform access, model inference and cloud compute ^[27]. Figures below are the published rates as of 1 October 2026.

Kilo Pass, launched in January 2026, sells a monthly credit amount and adds bonus credits that grow with subscription streak; the published tiers are Starter at $19 per month, Pro at $49 and Expert at $199 ^[27][40]. Fortune reported that the product went from idea to launch in three days and was built end to end by a single engineer, Igor Šćekić, with no product requirements document ^[41]. A 14-day trial is an Enterprise trial, after which teams choose Teams or Enterprise ^[27].

Licensing, openness and privacy

The current repository is MIT licensed, covering the VS Code extension, the JetBrains plugin and the CLI; the legacy repository remains under Apache-2.0 ^[5][27][32]. Kilo's FAQ states that hosted services such as the Gateway, Cloud Agents and team administration "add managed infrastructure and enterprise controls" on top of the open-source agent ^[28]. In February 2026 the company said it intended to make its backend infrastructure repositories source-available, with the exception of a small component used to detect and prevent abuse of its agents for illegal or harmful tasks ^[39]. The Anaconda announcement refers to "Kilo's open source and source-available codebase" ^[42].

The CLI privacy policy states that code and prompts are transmitted to the model provider the user selects, that Kilo does not have access to or store that data, and that API keys entered by the user are stored locally and sent only to the chosen provider ^[31]. It notes that running local models avoids sending data to third parties ^[31]. Kilo's marketing FAQ adds that it "never trains on your code" and that enterprise customers get SSO, audit logs, SOC 2 Type II certification and data-residency controls ^[28].

Telemetry is documented as configurable rather than absent. In VS Code, Kilo honours the editor's own telemetry.telemetryLevel setting; in the CLI, KILO_TELEMETRY_LEVEL=off disables it; and the CLI's OpenTelemetry export, which is enabled by default, is turned off by setting experimental.openTelemetry to false in kilo.jsonc. If OTEL_EXPORTER_OTLP_ENDPOINT is set, the CLI exports traces and logs to that endpoint, with internal span attributes still carried under an opencode.* namespace ^[25][26]. The in-product message-feedback buttons are part of telemetry and disappear when it is off ^[25].

A separate sandbox adds an operating-system boundary around agent tools, limiting where they can write and, by default, blocking outbound network access from model-originated commands. It is disabled by default, is not available on Windows, does not restrict reads, and refuses to run an affected tool rather than silently falling back to unrestricted execution if an enabled policy cannot be enforced ^[22]. Project configuration can tighten a sandbox policy but cannot disable a globally enabled one ^[22].

Adoption

Install and download counters measure different things and overlap; Kilo itself cautioned in May 2026 that "marketplace counters overlap" and that "installs are not retention" ^[8]. The company's own headline figures have moved quickly: more than a million downloads in February 2026 ^[39], "over 2.2 million developers" on the old extension in April 2026 ^[10], "3M+ Kilo Coders" and more than 40 trillion cumulative tokens in May 2026 ^[8], "more than 3 million developers" in Anaconda's July 2026 announcement ^[42], and "5M+ Kilo Coders" with "10T+ tokens processed every month" on the home page in October 2026 ^[28][42].

OpenRouter rankings

Kilo Code is one of the largest consumers of OpenRouter's API. OpenRouter's own app page for Kilo Code, read on 1 October 2026, reported 17.3 trillion total tokens, a daily global rank of #2 among tracked applications, 393 distinct models used, activity since April 2025, and category positions of #1 in IDE Extensions, #2 in Coding Agents and #2 in CLI Agents ^[43].

On OpenRouter's Top Apps leaderboard for the trailing week, with usage data through 30 September 2026, Kilo Code ranked fourth. OpenRouter states that each window ends with the most recent complete daily bucket, so figures read on different days differ because the window has advanced; the totals below were read on 2 October 2026 ^[44]:

These are usage snapshots, not quality measures. OpenRouter states that its rankings count prompt and completion tokens routed through its API, aggregate them into daily UTC buckets, exclude requests users or apps keep private, and that its model charts and leaderboard "do not rank models by accuracy, reasoning ability, or benchmark performance" ^[44]. Positions differ by window: OpenRouter's one-day chart on the same date placed Kilo Code second rather than fourth ^[44]. The underlying model mix also shifts; OpenRouter's app page listed Space Bunny Alpha, Poolside's Laguna S 2.1 and NVIDIA's Nemotron 3 Ultra as the three models Kilo Code sent the most tokens to in the month to 30 September 2026 ^[43].

CNBC reported in December 2025 that Kilo Code was then "the most widely used service for startup OpenRouter's application programming interface" and had processed more than 3 trillion tokens in the previous month according to OpenRouter ^[38].

Company, funding and acquisition

Kilo Code, Inc. was founded in early 2025 by Scott Breitenother, who is chief executive, and Sid Sijbrandij, co-founder and former chief executive of GitLab ^[38][41]. CNBC reported that Sijbrandij, who stepped down as GitLab's chief executive in 2024 while remaining board chair, was introduced to Breitenother in September 2025 and offered him a job within 25 minutes of their first meeting; Breitenother had previously founded and sold the consultancy Brooklyn Data ^[38]. Sijbrandij contributed early capital, and the company employed about 34 people at the time of the report ^[38]. Kilo is remote-first with offices in San Francisco and Amsterdam ^[29].

The company announced an $8 million seed round on 10 December 2025. CNBC listed Breakers, Cota Capital, General Catalyst, Quiet Capital and Tokyo Black as backers ^[38]; FastForward reported the round as led by Cota Capital with the other four participating ^[39]. CNBC also noted a GitLab filing disclosing that GitLab paid Kilo $1,000 for a 10-business-day right of first refusal should Kilo receive an acquisition proposal before August 2026 ^[38].

On 15 July 2026 Anaconda announced that it was acquiring Kilo Code, in a post co-written by Anaconda chief executive David DeSanto and Breitenother ^[42]. The post frames the deal as combining Anaconda's package, environment and governance layer with Kilo's "agentic engineering layer", and states that "Kilo alone orchestrates almost 10 trillion tokens per month across more than 3 million developers" ^[42]. DeSanto is quoted saying "There's been no real answer to token-maxxing. Organizations are spending enormous sums, with very little visibility into where the risk is and if they are getting an ROI", and Breitenother saying "Developers aren't going to stop using AI. The question is whether enterprises are going to own that experience end to end or just hope for the best" ^[42]. The announcement says Kilo "remains available for individual builders, teams, and organizations" and reports that early customers running agents through the Anaconda Platform saw "30 to 50% reductions in token consumption" ^[42]. It does not state the financial terms. Anaconda announced its acquisition of the AI security company Enkrypt AI on 4 August 2026, and Kilo shipped Enkrypt AI model safety scores on 10 September 2026 and an Enkrypt AI guardrails integration on 25 September 2026 ^[45][30].

Reception

Kilo has been covered mainly as a fast-moving, open-source alternative to subscription coding tools. CNBC's December 2025 piece framed the company around Sijbrandij's involvement and quoted a Dutch e-commerce engineer, Daniël Langezaal of Plug&Pay, saying about 80% of his company's developers had moved to Kilo Code after trying tools from Anthropic, Cursor and Microsoft ^[38]. VentureBeat's February 2026 review of Kilo CLI 1.0 described the launch as "a strategic pivot away from the IDE-centric 'sidebar' model" and placed the CLI in direct competition with Claude Code and Block's Goose ^[40]. FastForward called Kilo "an early-stage open source agentic development platform" and highlighted its refusal to mark up token costs ^[39]. Fortune's March 2026 feature focused on the company's organisational choice to operate with no product management layer, with Breitenother describing engineers as "mini CEOs" of their own products and conceding that "minor inconsistency is an acceptable price for speed" ^[41].

Reception inside the user base has been more mixed around the February-to-April 2026 rebuild. The GA announcement itself acknowledged that provider configuration, code indexing and other features had not all made the jump at once, and the pre-release post offered $100 in Kilo credits for merged bug-fix pull requests ^[9][10]. The documentation's own migration notes record that codebase indexing was "temporarily unavailable in the new extension" after the rebuild ^[26], and Kilo's blog later announced its return in June 2026 ^[30]. The Visual Studio Marketplace rating sat at 3.87 out of 5 from 214 ratings on 1 October 2026, and the Open VSX listing showed 3.38 from 21 reviews ^[34][35].

When Roo Code announced in April 2026 that it would shut down its products on 15 May 2026 to concentrate on a cloud agent, Kilo published an acknowledgement of its parent project, crediting Roo with "custom modes, the Architect/Code/Debug split, diff-based editing" and telling former Roo users that "the codebases share a grandparent" ^[7]. Kilo also publishes a Roo-to-Kilo migration guide ^[5].

See also

• Cline
• Roo Code
• opencode
• Claude Code
• Harness (AI)
• AI coding agent
• Model Context Protocol
• OpenRouter
• Cursor
• GitHub Copilot
• Aider

References

1. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8"Kilo-Org/kilocode: Kilo is the all-in-one agentic engineering platform." README, GitHub. github.com/...kilocode (read 1 October 2026)
2. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8 ^9 ^10 ^11 ^12 ^13 ^14GitHub REST API repository metadata for `Kilo-Org/kilocode`, including creation date, licence, stars, forks and release tags. api.github.com/...kilocode (read 1 October 2026)
3. ^1 ^2 ^3 ^4"GitHub - Kilo-Org/kilocode: Kilo Code (forked from Roo Code) gives you a whole dev team of AI agents in your code editor." Internet Archive capture, 26 March 2025. web.archive.org/...kilocode
4. ^1 ^2 ^3"GitHub - Kilo-Org/kilocode: Open Source AI coding assistant for planning, building, and fixing code. We're a superset of Roo, Cline, and our own features." Internet Archive capture, 11 May 2025. web.archive.org/...kilocode
5. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8"Kilo-Org/kilocode-legacy" README and repository metadata (Apache-2.0, archived). github.com/...kilocode-legacy (read 1 October 2026)
6. ^1 ^2 ^3"Kilo-Org/kilo" README and repository metadata (archived, "This repo has been moved"). github.com/...kilo (read 1 October 2026)
7. ^1 ^2 ^3 ^4Brian Turcotte. "Thank you, Roo! We'll take it from here." Kilo Blog, 21 April 2026. blog.kilo.ai/...thank-you-roo
8. ^1 ^2 ^3 ^4Brendan O'Leary. "What We Learned from 3 Million Downloads of Kilo Code." Kilo Blog, 29 May 2026. blog.kilo.ai/...e-learned-from-3-million-downloads
9. ^1 ^2 ^3 ^4 ^5Arkadiy Kondrashov. "We've completely rebuilt the Kilo Code extension for VS Code. Join the beta test." Kilo Blog, 10 March 2026. blog.kilo.ai/...rebuilt-the-kilo-vs-code-extension
10. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8Job Rietbergen. "The New Kilo Code for VS Code Is Now Generally Available." Kilo Blog, 2 April 2026. blog.kilo.ai/...new-kilo-for-vs-code-is-live
11. ^1 ^2 ^3Brendan O'Leary. "Kilo Code Goes Native on JetBrains." Kilo Blog, 9 July 2026. blog.kilo.ai/...kilo-code-goes-native-on-jetbrains
12. ^1 ^2 ^3Brendan O'Leary and Johnny Eric Amancio. "Introducing Kilo Memory: Project-Scoped Memory for Your Agents." Kilo Blog, 22 July 2026. blog.kilo.ai/...introducing-kilo-memory
13. ^1 ^2"Using Agents." Kilo Code documentation. kilo.ai/...using-agents (read 1 October 2026)
14. ^1 ^2 ^3"Orchestrator Mode (Deprecated)." Kilo Code documentation. kilo.ai/...orchestrator-mode (read 1 October 2026)
15. ^1 ^2 ^3"Custom Subagents." Kilo Code documentation. kilo.ai/...custom-subagents (read 1 October 2026)
16. ^1 ^2 ^3 ^4 ^5 ^6 ^7"Memory." Kilo Code documentation. kilo.ai/...memory (read 1 October 2026)
17. ^1 ^2"Skills." Kilo Code documentation. kilo.ai/...skills (read 1 October 2026)
18. ^"Marketplace." Kilo Code documentation. kilo.ai/...marketplace (read 1 October 2026)
19. ^"MCP Overview." Kilo Code documentation. kilo.ai/...overview (read 1 October 2026)
20. ^"AI Gateway." Kilo Code documentation. kilo.ai/...gateway (read 1 October 2026)
21. ^"Auto Model." Kilo Code documentation. kilo.ai/...auto-model (read 1 October 2026)
22. ^1 ^2"Sandboxing." Kilo Code documentation. kilo.ai/...sandboxing (read 1 October 2026)
23. ^1 ^2"Cloud Agent." Kilo Code documentation. kilo.ai/...cloud-agent (read 1 October 2026)
24. ^"Gas Town by Kilo." Kilo Code documentation. kilo.ai/...gastown (read 1 October 2026)
25. ^1 ^2 ^3 ^4"Kilo Code CLI: AI Coding Agent in Your Terminal" and "Message Feedback." Kilo Code documentation. kilo.ai/...cli and kilo.ai/...message-feedback (read 1 October 2026)
26. ^1 ^2 ^3"Kilo Code for JetBrains" and "What's New in Kilo Code (April 2026)." Kilo Code documentation. kilo.ai/...jetbrains (read 1 October 2026)
27. ^1 ^2 ^3 ^4 ^5 ^6"Kilo Code Pricing: Free, Teams, Enterprise & Usage Costs." kilo.ai/pricing (read 1 October 2026)
28. ^1 ^2 ^3 ^4 ^5"Kilo - Open Source AI Coding Agent in IDE, CLI and Cloud." kilo.ai (read 1 October 2026)
29. ^"About Kilo Code - Open-Source AI Coding Orchestration." kilo.ai/about (read 1 October 2026)
30. ^1 ^2 ^3 ^4 ^5"Kilo Code in the Press - Coverage, Reviews & Media" and the Kilo Blog post archive. kilo.ai/press and blog.kilo.ai (read 1 October 2026)
31. ^1 ^2"Kilo CLI Privacy Policy." PRIVACY.md, Kilo-Org/kilocode. github.com/...PRIVACY.md (read 1 October 2026)
32. ^1 ^2 ^3MIT License file, Kilo-Org/kilocode. github.com/...LICENSE (read 1 October 2026)
33. ^"Contributing to Kilo CLI." CONTRIBUTING.md, Kilo-Org/kilocode. github.com/...CONTRIBUTING.md (read 1 October 2026)
34. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8"Kilo Code: AI Coding Agent, Copilot, and Autocomplete." Visual Studio Marketplace listing and gallery extension-query metadata. marketplace.visualstudio.com/items (read 1 October 2026)
35. ^1 ^2 ^3Open VSX registry entry for `kilocode/kilo-code`. open-vsx.org/...kilo-code (read 1 October 2026)
36. ^1 ^2"Kilo Code." JetBrains Marketplace plugin 28350. plugins.jetbrains.com/...28350-kilo-code (read 1 October 2026)
37. ^1 ^2 ^3 ^4npm registry metadata for `@kilocode/cli`. npmjs.com/...cli (read 1 October 2026)
38. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8Jordan Novet. "Former GitLab CEO raises money for Kilo to compete in crowded AI coding market." CNBC, 10 December 2025. cnbc.com/...ion-for-kilo-to-compete-in-vibe-coding
39. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8Ron Miller. "Exclusive: Kilo Code bets on agentic engineering with a model-agnostic CLI spanning 500 AI models." FastForward, 3 February 2026. fastforward.blog/...tic-cli-spanning-500-ai-models
40. ^1 ^2 ^3 ^4 ^5 ^6 ^7Carl Franzen. "Kilo CLI 1.0 brings open source vibe coding to your terminal with support for 500+ models." VentureBeat, 4 February 2026. venturebeat.com/...g-to-your-terminal-with-support
41. ^1 ^2 ^3 ^4Sage Lazzaro. "How cutting out product management enabled Kilo to compete in the hyper-fast AI coding market." Fortune, 17 March 2026. fortune.com/...-in-the-hyper-fast-ai-coding-market
42. ^1 ^2 ^3 ^4 ^5 ^6 ^7 ^8David DeSanto and Scott Breitenother. "AI on Your Own Terms: Anaconda Acquires Kilo Code." Anaconda blog, 15 July 2026. anaconda.com/...anaconda-acquires-kilo-code
43. ^1 ^2 ^3"Kilo Code." OpenRouter App & Agent Rankings app page. openrouter.ai/...kilo-code (read 1 October 2026)
44. ^1 ^2 ^3"LLM Rankings." OpenRouter, Top Apps section, This Week view, usage data through 30 September 2026. openrouter.ai/rankings (read 1 October 2026)
45. ^"What It Means To Secure AI on Your Own Terms: Anaconda Acquires Enkrypt AI." Enkrypt AI blog, 4 August 2026. enkryptai.com/...anaconda-acquires-enkrypt-ai