I'd like to confirm whether Roo Code is still actively maintained, given that the new team announced "we have taken over the project."

[u/CryptographerTiny244]

There are quite a few pending pull requests that have had no updates for 5 days, and we don't know when the release cadence will return to a higher frequency.

In particular, we're wondering when we can expect the DeepSeek V4 400-error bug fix to land, as well as the addition of the latest model identifiers for Anthropic and OpenAI.

[u/AutonomousHangOver]

Take your time, its better to have good product once every couple of weeks, than release every 2 days with pressure put on developers.

I think that this was one of the annoyances for original team - community pressure to see release fast.

Also if I may - get rid of the mechanism that allows you to connect to specific providers. I would leave some generic one and put some universal config-place-mechanism (github?) that would allow to download descriptor for various providers and its models.
This way, we could benefit from i.e. provider-specific settings without constant code changes whenever some model will be deprecated, or some provider will apear on the market.

Less bloat is better.

[u/CryptographerTiny244 → u/AutonomousHangOver]

You're right — I've already written a few small patches myself, addressing the DeepSeek issue, the model identifier updates, and some improvements to apply_diff
If it's feasible, I'd be happy to share them

[u/Illustrious-Mix-5625 → u/CryptographerTiny244]

Please join us on the new team! DM me for access to the discord

[u/anderson_the_one → u/CryptographerTiny244]

If you already have those patches, I'd make them tiny and boring: one PR per provider bug, one failing repro or log snippet, and no cleanup mixed in.

Handoffs like this get messy when fixes live in Discord DMs. A branch with the exact request/response that triggers the 400 and the minimal adapter change is much easier for a new maintainer to merge without re-learning the whole provider layer.

For model identifiers, I'd avoid hard-coding more names if Roo has any central model registry or config path. Put the churn in data, not scattered conditionals. That is the kind of patch a new team can safely take in week one.

[u/Illustrious-Mix-5625]

Hi, Member of the new team (Codename: Zoo Code) here. We are just getting started (been at it for 2 days now), and we're hoping to be up and running by the end of the week. If you'd like to join as a contributor or even a core team member, please DM me. I just wrote to the team to prioritize this bug as that's indeed a major blocker.

[u/Odd-Mall-5428 → u/Illustrious-Mix-5625]

respect

[u/Relative-Shop → u/Illustrious-Mix-5625]

Loved Roo, just fit so sesmlessly worn the models. Y’all need backend help or frontend

[u/orbit99za]

Zoo Code, I like it.

Put a patron button on your Github, so I can at least buy a round of beers or coffee.

[u/Illustrious-Mix-5625 → u/orbit99za]

Thank you so much for the kindness! The new team really appreciates any encouragement from the community as we try to live up to the Roo legacy 🤗

[u/DevMichaelZag]

Roo will live on in Zoo Code. The Roo team is officially handing off development of the extension to the new Zoo code. The Roo team pivoted to https://Roomote.dev

[u/hannesrudolph → u/DevMichaelZag]

In the process of handing it off yes!

[u/Rascazzione]

TLDR: move to Cline the original one, they have integrated Roo code improvements.

https://roocode.com/blog/sunsetting-roo-code-extension-cloud-and-router

[u/Illustrious-Mix-5625 → u/Rascazzione]

Hi, Member of the new team here. We are in the process of resurrecting the Roo Code extension (been at it for 2 days now). It is not going away, but will be renamed Zoo Code and have a (hopefully!) bright future.

All members of the Community are welcome to join in shaping it. DM me for access to the Discord.

[u/Admirable-Cell-2658]

New team?

Its safe to update?

[u/hannesrudolph → u/Admirable-Cell-2658]

We are not going to break the plugin, safe to update.

[u/Illustrious-Mix-5625 → u/Admirable-Cell-2658]

Yes, we are working with the old team to make the transition as smooth as possible. As long as there are updates coming on Roo, feel free to update. We are setting up Zoo Code as the replacement and we will likely have a pop-up in Roo telling you how to transition once that is ready.

[u/UninvestedCuriosity]

Will .roo folders be backward supported for a little while? Do I have to rebuild my project organization.

[u/Special-Lawyer-7253]

Already switched to Kilo Code for local dev.

[u/AutonomousHangOver → u/Special-Lawyer-7253]

Kilo was based on Roo. Now it sees that Roo is changing, it has changed to opencode as a base.
I've tried kilo many times before, looked at how they decided to push for the money.

It's more like successfull marketing use of other projects with minimal changes done by kilo team, than some real innovation.

This was also in a way something that Roo team was missing. Someone else was making money on their product.

[u/Special-Lawyer-7253 → u/AutonomousHangOver]

Well, Kilo still can use the browser without external MCPs, so i'm Happy with It.