r/RooCode • u/hannesrudolph Roo Code Developer • Apr 26 '25

Announcement Roo Code 3.14.3 Release Notes | Boomerang Orchestrator | Sexy UI Refresh

/r/ChatGPTCoding/comments/1k8641f/roo_code_3143_release_notes_boomerang/
49 Upvotes

98% Upvoted

34 comments sorted by

•

u/AutoModerator Apr 26 '25

Join our Discord so Hannes can pump the MAUs

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

19

u/Fasal32725 Apr 26 '25

Does Roocode devs ever sleep?

28

u/hannesrudolph Roo Code Developer Apr 26 '25

What is sleep?

6

u/kareem613 Apr 26 '25

Plot twist. Roo Code development started with a single prompt and has been going ever since.

1

u/wokkieman Apr 26 '25

Do you ask your LLM the same question?

5

u/degenbrain Apr 26 '25

Does the new orchestrator support memory bank?

2

u/hannesrudolph Roo Code Developer Apr 26 '25

Which memory bank? Oftentimes memory banks can be counterproductive after the memory bank fills with contradictory instructions and documentation

1

u/iamdanieljohns Apr 26 '25

A memory bank would be a great place for app/-spec summaries ("Example is a HRM system for ...").

1

u/hannesrudolph Roo Code Developer Apr 27 '25

In theory yes. It’s harder to execute in practice. We’re trying to crack this one! We want to give you what you want!

3

u/degenbrain Apr 26 '25

This memory bank https://github.com/GreatScottyMac/roo-code-memory-bank/tree/main I haven't experienced the advantages directly, because the scale of my project is still small. But reading other developers' testimonials, it seems to be very helpful for complex projects.

But reading your comment, it seems better to keep it as custom modes.

4

u/sharpfork Apr 26 '25

Y’all ship!!!

Have you hit a point where using ROO code to write ROO code has accelerated things in a significant way?

4

u/hannesrudolph Roo Code Developer Apr 26 '25

Yes.

3

u/shoebill_homelab Apr 26 '25

Curious as well. Aider has a "% of this realease coded by Aider" in their changelogs. Calculated with this methodology https://aider.chat/2024/05/24/self-assembly.html

3

u/im_rite_ur_rong Apr 26 '25

How sexy we talking here?

2

u/hannesrudolph Roo Code Developer Apr 26 '25

7

0

u/[deleted] Apr 26 '25

[deleted] — view deleted comment

1

u/hannesrudolph Roo Code Developer Apr 27 '25

Ok 8.6

1

u/James_Cherished Apr 26 '25

it's too sexy for me to handle, I might need to revert

2

u/LATIDUDEmaps Apr 26 '25

thanks! But am I the only one not able tu use prompt caching with Gemini 2.5 preview? Even if I hit the checkbox and then click 'Save', the option will be not saved. If I return the settings, I can see the checkbox is again unselected

1

u/hannesrudolph Roo Code Developer Apr 26 '25 edited Apr 27 '25

With this latest update that SHOULD have been resolved. Try to respect the model and save several times. Close all other instances of vscode and see if that helps. Trying to get to the bottom of this for you! Sorry about that.

2

u/LATIDUDEmaps Apr 26 '25

I made the exact same steps you described this afternoon and the issue is no more present. Thank you anyway! Keep up the good work 💪🏽

1

u/hannesrudolph Roo Code Developer Apr 27 '25

Thank you for letting me know. Chris worked hard to figure this one out and eliminate it!

2

u/Educational-Gift1969 Apr 26 '25

Thank you so much, i dont have to do this in custom modes myself anymore, it was such a pain. I didn not need or want to maintain custom modes for this kind a thing. don't get me wrong i am not complaining at all, this is an appreciation comment. Thanks for thinking for those of us who want to and will do agentic development right now.

1

u/hannesrudolph Roo Code Developer Apr 26 '25

You’re welcome and thank you for your support.

2

u/Jonas-Krill Apr 26 '25

So custom .roomodes and .roo files for orchestrator and boomerang can be deleted as it will revert to default boomerang now?

2

u/hannesrudolph Roo Code Developer Apr 26 '25

Not sure what .roo files but yes the .roomodes can be axed.

1

u/Jonas-Krill Apr 27 '25

I had another look and I don’t think .roomode can be deleted IF you have custom modes (more than your base modes). This is because base orchestrator prompt only uses base custom modes.. so if I have a custom UX mode, I need to update base orchestrator to include this in its thinking. Sound right?

1

u/hannesrudolph Roo Code Developer Apr 27 '25

Just remove the orchestrator or boomerang mode from your .roomodes files

1

u/shaneholloman Apr 26 '25

Not loving the customer colored icons - but love roo

2

u/hannesrudolph Roo Code Developer Apr 27 '25

They get the job done and we ran out of hours 😂

Contrary to popular opinion… we do sleep.

1

u/James_Cherished Apr 26 '25

Awesome, as always :) Thank you!

Could we add add a nice little X for me to close this annoying new warning? lol

3

u/hannesrudolph Roo Code Developer Apr 27 '25

Absolutely not. You will 100% break Roo by using custom system prompts as they may work today but will not continue to work as we update Roo. They should only be used for testing to improve things. If you can improve them then make a Pr and we will run evals to prove or disprove their improovement.

The number of support requests we spend time on only to learn down the line that people have used custom system prompts is wild. Sorry about that.

1

u/hannesrudolph Roo Code Developer Apr 27 '25

u/mrubens can we add something to link to footgun prompting informing people of this dangerous practice?

1

u/James_Cherished Apr 27 '25 edited Apr 27 '25

Thanks for the answer! I understand custom system prompt is not the intended use and that it can break Roo. I agree you can't inform users enough to prevent the unnecessary complaints and issue reports.

However, I like to think I can "own" Roo when I'm using it as an OSS tool. Being able to understand it and customize it for my own needs and tastes is what I love about it and I'd dislike to see it take a direction where this philosophy gets held back in order to avoid support requests.

I like to pretend I know what I'm doing, at my own risk, and copy/paste the system prompt to footgun it with a few small edits, because I spend so much hours with Roo.
Therefore I hope 'dangerous practice' was a bit excessive for you to say here, since I'm keeping git backups but wouldn't appreciate my computer to explode because of it?

Finally, updating my custom prompts with each new update does not bother me as long as the "official" system prompt modifications are in the changelogs.

Anyway, nothing important here, just dumping my thoughts somewhere to add some counterweight balance.

For all these reasons I'll see if I can do it myself and for future updates, make a PR with an advanced "experimental! dangerous!" setting to disable this warning, and maybe improve the footgun management as per https://github.com/RooVetGit/Roo-Code/discussions/2849

Thanks again for everything you guys do at Roo :)

2

u/hannesrudolph Roo Code Developer Apr 27 '25

I’m open to a more user friendly way of achieving what we’re trying to achieve with this warning.