zlacker

How are you differentiating from the cline/roo's of the world?

>>htrp+(OP)
Our plan is to be a superset of Cline and Roo's features (we already have all the major features from both) [0]

We also have our own provider, which means no need to bring your own API keys (you can if you like, but it is batteries included by default) and we're not charging anything on top of the API pricing. Instead of monetizing on individual developers, we want it to be free for them and make money eventually off enterprise contracts [1]

[0]: https://blog.kilocode.ai/p/roo-or-cline-were-building-a-supe... [1]: https://kilocode.ai

>>bolear+qn
I can't find any reference to Cline/Roo charging anything on top of API pricing.

Not sure how they'd do it considering you bring your own API keys. Can you link me to a resource?

>>alasan+UD
GP didn't say Cline/Roo charged anything on top.

>>oofbar+uJ
The comparison table on the kilo site says "OpenRouter without 5% markup" and only puts a checkbox next to kilo.

>>alasan+LO
Roo/Cline doesn't offer Openrouter, markup or not.

>>jychan+H41
You can most definitely use Openrouter with Roo and Cline. Openrouter leaderboards are dominated by these 2 apps.

>>bolear+qn
maybe you could answer a question about kilo usage: If I choose Google Gemini as the API provider and give it my Gemini API key, why does it say that I'm low on credits (and I get API request failures immediately)? As far as I understand gemini 2.5 pro preview is free to use. (and in Cline I'm able to choose Google Gemini as the API provider & provide my API key and it will successfully make API requests)

>>thetur+Bb1
But they don't OFFER Openrouter a paid product... You cannot give roo/cline dollars and get openrouter api access.

>>UncleO+Zh1
It looks like a bug to me. Did you report it on GitHub?

>>alasan+LO
Yes - with our built-in provider, we provide all the models that OpenRouter provides but without OpenRouter's 5% markup. We provide them at cost (the AI provider cost)

>>UncleO+Zh1
We added it to the issues: https://github.com/Kilo-Org/kilocode/issues/349

>>UncleO+Zh1
Hey, we can't reproduce it. Could you maybe jump in and give some more details? https://github.com/Kilo-Org/kilocode/issues/349