A Core Merge Is Not a Feature
The work isn’t done when the PR merges. It’s done when someone can use it. A word from our VP of Engineering Emilie Schario Nobody uses Kilo Core directly. They use VS Code, JetBrains, the CLI, Agent Manager, or Desktop. Core is the shared code that powers all of those experiences. This distinction matters because merging code is not the same thing as shipping value to a customer. At Kilo, we've…
A core merge is not a feature, according to Kilo's VP of Engineering Emilie Schario. The company focuses on delivering value to users as quickly as possible, rather than organizing work around monthly releases or big launches. Engineers at Kilo can release changes multiple times a week without needing permission, and this frequent release cycle allows for immediate feedback and continuous improvement.
The company emphasizes releasing to one client first, rather than waiting for every client to implement the same functionality. This approach provides real user feedback without waiting for all clients to be ready, and allows subsequent clients to build upon successful functionality. This strategy was demonstrated with Kilo Swarm, which was first shipped to VS Code, then exposed through shared Core code, and finally enabled by default across clients. By the time Swarm was enabled by default, users had already been using it for nearly two weeks.
Maintaining consistency across clients requires discipline and clear communication, but it is essential to avoid a fragmented product where functionality depends on the client being used. The Enhance Prompt feature, which was shipped first in VS Code and later in JetBrains, Agent Manager, and Desktop, serves as an example of the need for explicit follow-up work. The underlying functionality was already in Core, but the missing client-specific UI delayed its availability.
The key takeaway is that sometimes, going slow to go fast is necessary, especially when building shared infrastructure in Core. However, teams should strive to avoid overanalyzing or delaying decisions, and instead focus on shipping useful improvements as quickly as possible to gain valuable user feedback.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.