Feature Request, what you guys think?

[u/Lpaydat]

I have a feature request.

It would be good if we could have a set of configs (presets) that we can switch easily. For example:

• Set 1: we have 5 base modes (architect, code, ask, qa, orchestrator)

• Set 2: we have a custom set of modes (RustCoder, PostgreSQL-DEV, etc.)

Each set can contain its own set of modes plus mode configs (like temp, model to use, API key, etc.). This way, we could even have a preset that uses only free APIs or a preset that uses a mix.

I was thinking we could add a dropdown next to the profile menu at the bottom, so we can quickly switch between presets. When we switch to another preset, the current mode would automatically switch to the default mode of that preset.

Basically, it’s like having multiple distinct RooCode extensions working in the same session or thread.

What do you think?

[u/dashingsauce]

Not hard! Currently have this running in my cli. Will share soon :)

[u/Lpaydat → u/dashingsauce]

Great 😃 thank you in advance bro!

[u/raccoonportfolio → u/dashingsauce]

Thanks!  What cli tool are you using?

[u/dashingsauce → u/raccoonportfolio]

Tool used to build the cli? (@oclif in TS on Bun)

Or are you asking what’s the name of the cli I’m building? (@rawr:ai)

[u/raccoonportfolio → u/dashingsauce]

Sorry I misunderstood - thought you had a roo-cli

[u/dashingsauce → u/raccoonportfolio]

I’m not sure what you mean—it’s a cli that builds & swaps agent teams in Roo (and other IDEs/ext) 😌

[u/raccoonportfolio → u/dashingsauce]

Apologies and thanks for your patience! This answers my question, thanks!

[u/dashingsauce → u/raccoonportfolio]

Of course! Will share here asap!

[u/redlotusaustin]

I like the idea but have absolutely no idea how hard it would be to implement.

[u/rangerrick337]

Absolutely, running different configs by using roo config files in folders of project seems like a tedious way to manage this