What's great
What stood out to me is the developer experience — it feels fast to get value without a bunch of setup friction.
Clear, focused UX that stays out of the way while coding
Helpful suggestions for refactors and “what’s the next step” moments
Customization is there when you need it, but the defaults are sensible
Output quality is consistently usable (less time fighting the assistant)
Overall, it’s the kind of tool you can keep open all day and trust as a teammate.
What needs improvement
Two areas I’d love to see improved:
Pricing / cost clarity: a simple, transparent breakdown (what drives cost, typical ranges, and a few real examples) would make it easier to recommend to teams.
Integration & onboarding: more “copy-paste” quickstarts (CLI + common editors), stronger docs for edge cases, and a few ready-made templates for common workflows would reduce the learning curve.
Did the MCP marketplace integrations add real day-to-day value?
Yes — but only once you curate a small set of MCPs you actually use. When the right tools are one click away (docs/search, tickets, repo utilities, etc.), it reduces context switching and keeps the workflow inside the agent loop.
The main risk is “tool sprawl”: too many options can add noise. A favorites/pins flow + per-project recommended MCP packs would make the marketplace even more practical.
How detailed and useful are cost and usage analytics?
Useful for staying honest about spend — I like having a clear view of usage over time and what’s driving it.
What would make it even better (especially for teams) is deeper attribution: cost per session/task/PR, breakdown by model + tools, plus budgets/alerts and an export (CSV) for reporting. That level of detail is what turns “analytics” into real cost control.
How does it compare to Roo or Cline in practice?
In practice it feels closest to the “agentic editor” workflow you get with Cline/Roo: plan → make file edits → run/iterate.
Where Kilo Code stands out for me is day-to-day ergonomics: it feels lighter-weight, faster to get started, and the UX stays out of the way during quick iterations. Roo/Cline still tend to win if you want maximum configurability and more knobs for edge cases.
Net: Kilo Code is great for consistent, repeatable “edit + test + iterate” loops; I’d reach for the others when I need deeper customization.
What's great
Congrats on the launch 👏
Really like the positioning here — the “no editing, no timeline, just present” angle is super clear.
Live layout switching + recording that’s done when you stop talking solves a very real pain for people who present a lot on camera. Feels especially useful for demos, tutorials, and founder updates.
Curious to see how teams adopt this alongside Zoom/Meet workflows. Nicely executed.