VS Code extensions are the new coding agent battleground

The community just forked Roo Code into Kilo Code, and it's already better than the original. Open source moves fast when developers are scratching their own itch.

But here's what matters more than the fork drama: VS Code extensions are becoming the new battleground for coding agents. Not standalone apps. Not web interfaces. Extensions.

Why? Because your coding agent needs to live where your code lives. When it's fighting with window switching, file navigation, and context loss every 30 seconds, you're not building — you're babysitting.

I've been running coding agents in three different environments for the past month:

• Terminal-only agents: Fast, scriptable, but blind to your actual workflow
• Web-based agents: Pretty interfaces, but they're always one tab-switch away from losing context
• Editor-integrated agents: They see what you see, edit what you edit, and never lose the thread

The difference isn't subtle. It's the difference between describing your code to someone over the phone versus pair programming.

Here's the pattern that's emerging: the best coding agents aren't trying to replace your editor. They're trying to become part of it.

Kilo Code gets this. Instead of building another standalone coding assistant, they built something that lives in your sidebar, reads your open files, and understands your project structure without you explaining it every session.

Your coding agent should know which files you have open, which line you're on, and what you changed in the last commit — without asking.

But integration isn't enough. The agents that actually ship code have three things in common:

1. Session persistence
They remember what you were working on when VS Code crashed. They pick up where you left off when you reopen the project next week.

2. File-aware context
They don't re-read your entire codebase every conversation. They know which files matter for the current task and load context accordingly.

3. Execution boundaries
They can run tests, start dev servers, and check build status — but they can't push to production or delete your .git folder.

The fork wars will continue. Roo Code will probably fork Kilo Code back. Someone will build a Claude-native version next month.

But the real innovation isn't happening in the models or the UIs. It's happening in the integration layer. The agents that win are the ones that feel like they belong in your development environment, not like visitors from another app.

If you're building coding agents, stop thinking about chat interfaces. Start thinking about development workflows. Your agent should feel like a really good pair programming partner who happens to live in your editor.