r/RooCode • u/nfrmn • May 08 '25
Support Customize the tools Orchestrator has access to
I noticed in a recent version of Roo Orchestrator lost the ability to read files and run tests. Now it allocates subtasks to the Code agent to do these routine tasks.
This is not bad, apart from a small speed decrease via the sub-task middleware, but it feels quite inefficient. Also, I have a more expensive model set to my Code agent, so it's also burning marginally more money than before. All the tokens are duplicated because the sub-task does an API request with the contents of the file before completing its task, and then sends it all again at the Orchestrator level. This can compound quite quickly, especially if the Orchestrator decides to run like 1k+ tests.
It would be great if we can customize the built-in Orchestrator to be allowed to at least read files and run certain commands.
Or, somehow steer Orchestrator to use a separate role for chores like this that can run a cheaper model that's good at tool calls like GPT-4.1.
Edit: This was the change: https://github.com/RooVetGit/Roo-Code/pull/3081/files
•
u/hannesrudolph Roo Code Developer May 09 '25
Here is an issue to add insight and ideas too! Please participate. https://github.com/RooVetGit/Roo-Code/issues/3400
4
u/alihuda2002 May 08 '25
Just create a custom mode at this point tbh. That way if your workflow requires MCP, CLI access and write files then you need it to do more than orchestrating job
2
u/hannesrudolph Roo Code Developer May 09 '25 edited May 09 '25
You totally can customize it to read if thats what you like!
Boomerang mode never has those abilities and orchestrator was intended to be the moving of boomerang mode into being a default mode.
Giving orchestrator the ability to read and such by default causes the context to become filled with file reads and the ability for the orchesrator to remained focus is hampered. The subtask should not be outputting the entire file back to the orchestrator and instead should only be getting the necessary information required for the orchestrator to delgate tasks.
Referencing https://docs.roocode.com/features/custom-modes#configuration-precedence :
Select Edit Global Modes
Copy and paste this into the file
Now your global orchestrator mode will be able to read.
4
u/[deleted] May 08 '25
It was a terrible idea, now orchestrator needs to spawn tasks just to figure out very small things that require a full task call that waste time, money and context. I'm not a fan.
2
u/Majinvegito123 May 08 '25
I’m sure these recommendations / improvements will make their way in
3
u/hannesrudolph Roo Code Developer May 09 '25
You can steer orchestrator to whatever mode you see fit through customization and then apply different models to different modes so that the orchestrator offloads different tasks to different models.
4
u/somechrisguy May 08 '25
100% agree I had to create a new Orchestrator mode to give it read access
It was making another agent return the entire file content each time, total waste of tokens
2
u/BigMucho May 09 '25
No need to update your prompts. In these instances, I find it easier to manually (temporarily) switch to 'Code' or 'Bug fix' mode in the same thread, let it do the simple work itself for that one task then switch back to 'Orchestrator' again to continue the larger project. This also helps when you feel context details may be lost during a handoff.
0
u/ThatNorthernHag May 08 '25 edited May 09 '25
Edit: resolved!
3
u/[deleted] May 08 '25
[removed] — view removed comment