r/RooCode

ok what is the baseline setup i need. is it better to use kimi's own cli or antigravity + open code + kimi api key?

ive been talking to gemini pro asking questions and this it what i got.

we also know roo code works with it too, any reason one would go with open code not roo code?

we know we need the stupid open code terminal thing coz antigravity does not support kimi directly right?

can we use the api key from a third party kimi provider with the kimi cli app?

would buying the $19 month kimi be worse or better than kimi api for coding landing pages?

I know that the recommendation is Cline, but I didn't liked. What I liked about Roo is the control it gave to their workflow. I prefer an assistant rather than an autonomous "agent". I tried Continue.dev last year and it was clunky. Is it better now?

I know that roo code will get some forks. But sadly, I cannot use them until they get traction.

Like a lot of you, I didn't take the archiving news well. Roo Code is my daily driver and I'm not ready to let it go.

So I'm forking it. New name, new org, same codebase, community-maintained. I've been in contact with the Roo team and they're supportive of the effort.

We're a team of 3 right now and looking for 2 more core maintainers who want to actively shape where this goes.

Ideally you have have TypeScript knowledge, experience with VS Code extensions or LLM APIs, and be able to put in consistent time (TBD). If you've contributed to Roo Code before, even better!

DM me if you're interested

Hi Hans and the team,

I totally respect the pivot to Roomote, but I’m honestly gutted to see Roo Code go. For many of us, Roo has become our favorite tool because it’s just... better. It has its own unique strengths that we really don't want to lose.

Instead of a complete shutdown or folding it back into Cline, would you consider looking for people within this community to take the mantle?

There are a lot of passionate developers here who use Roo every day. Maybe you could find a few vetted volunteers you trust to keep the project moving and preserve what makes it special?

It would be a shame to see such a great tool disappear. Thanks for everything you've built, and I hope there's a way to keep the spirit of Roo alive.

Hey, although it may sound wrong, but the rationale behind this is so that we as community can take it forward if the RooCode team is planning to stop development on this, which it seems lately. I know we can always fork, but still to avoid any fomo of RooCode coming back, which we want, but if there are plans already decided for this RooCode, we can take it forward and let community build it going forward. We can vote for new mods and core developers who are willing to contribute here.

[removed]

I put in a prompt for a very specific modification and Roo technically achieved what I wanted but in a clunky way by modifying a conditional inside the parent conditional when the more cleaner/correct solution was to modify the patent conditional.

So I used the same prompt but told it the specific line number of the parent conditional I wanted modified. It kept applying the same edit to the child conditional almost as if it was just reusing the previous prompt and ignoring the line number specification.

How do you get around this?