Buyer guide · agentic harnesses
Migrating from Roo Code to Kilo Code
Roo Code’s extension shut down on May 15, 2026. Kilo Code is one alternative with its own IDE/CLI surfaces; this guide covers installation, credential setup, project rules, and platform differences without assuming settings auto-port.
Who this is for: Teams migrating from Roo Code to Kilo Code on VS Code or JetBrains after Roo’s discontinuation — especially those with existing .roorules, provider keys, and terminal workflows to preserve.
What actually matters
- Install from the official Marketplace path (kilocode.Kilo-Code on VS Code); JetBrains plugin feature depth may differ from Roo’s old surfaces.
- API keys and provider auth do not auto-port — expect full re-authentication on every provider.
- Use the installed Kilo client's documented login and provider settings; published CLI guides disagree on credential paths, so do not assume one universal location.
- Kilo's migration wizard can map Roo rules and MCP configuration. Review the result alongside AGENTS.md and re-authenticate provider keys held in VS Code SecretStorage.
- Verify test commands and file permissions on a disposable branch before trusting the first autonomous edit.
- Optional @kilocode/cli extends terminal workflows — decide IDE-only vs IDE-plus-CLI before rollout.
ACE recommendation
Install Kilo from the official Marketplace path, re-authenticate every provider, consolidate rules into AGENTS.md, pilot on a sanitized repo, and read Kilo’s platform docs before assuming Roo parity.
Useful comparisons
How to run this decision
- 01Preserve Roo settings and project rules, install Kilo from the official Marketplace or JetBrains store, and disable the old extension after validating the migration.
- 02Re-authenticate every provider in Kilo settings — do not assume Roo-stored keys transfer.
- 03If using Kilo CLI, use kilo auth login or /connect and consult the installed version's documentation before changing scripts or credential paths.
- 04Merge .roorules and legacy .cursorrules content into AGENTS.md at the repo root; link or copy into Kilo’s rules format.
- 05Run the project test command manually, then ask Kilo to fix a trivial issue on a throwaway branch.
- 06Read Kilo’s platform docs for feature parity gaps vs Roo before committing team-wide.
Common pitfalls
- Assuming migrated rules and MCP configuration also transfer provider keys: keys held in SecretStorage require re-authentication.
- Treating a credential path from one CLI guide as universal despite conflicting published paths.
- Leaving conflicting .roorules and new Kilo rules — agents get contradictory instructions.
- Skipping re-test of permissions on a branch that touches CI or production config.
- Expecting JetBrains parity with VS Code without verifying feature list first.
Ask before you buy
- Are you installing from the VS Code Marketplace (kilocode.Kilo-Code) or the JetBrains plugin — feature depth can differ from Roo’s old surfaces?
- Which rules and MCP settings did the migration wizard map, and which providers need re-authentication? Check the installed client's documented auth flow instead of assuming a fixed credential path.
- Where did Roo project rules live (.roorules, .cursorrules)? Map them into AGENTS.md and Kilo’s rules format as one source of truth.
- Will you use the flagship IDE extension only, or also the optional @kilocode/cli for terminal workflows?
- Did you verify the test command and permissions on a disposable branch before trusting the first autonomous edit?
More buyer guides
Related decisions
Other harness buyer guides that answer the next question after this one.
Buyer guide
Editor vs terminal: which coding assistant workflow fits?
Choose the surface your team will actually use before comparing model quality.
Buyer guide
How to roll out an agentic harness without losing review discipline
A staged rollout pattern for teams that want speed without turning generated patches into unowned production risk.
Buyer guide
Agentic harness pricing: seats, tokens, and overage
Compare subscriptions and usage-based plans by the work they enable, not the number printed on the landing page.
Buyer guide
Coding-assistant myths in 2026: what the product pages blur
A myth-versus-reality check for coding assistants whose pricing, editor surfaces, privacy paths, and autonomy are easy to collapse into one misleading label.
Buyer guide
Enterprise AI coding assistant procurement checklist
A compact procurement block for security, legal, IT, and finance teams evaluating coding assistants beyond the demo and the seat price.
Buyer guide
Local LLM coding setup: Ollama, LM Studio, llama.cpp, and MLX
Pick a local inference stack and wire it to an agent harness without the usual traps — wrong ports, misconfigured context, untested quantisation, and mismatched API prefixes that make agents look broken when the model is fine.