At some point rovo dev was constantly corrupting files when editing them with "charencoding" issue.
Because of this, I added "Desktop Commander" MCP, but rovo would still always try it's own tool first, and I would have to not allow it, then ask to use the mcp.
Now I set it, with some other default tools, to "deny". It still always tries to use it's own default tools, even if I explicitly ask to use the mcp tools for editing and running bash commands.
I'll try the default tools again and see if this issue was resolved, but it should be possible to disable tools if I want to, so that the llm doesn't even knows about it, and won't try to use it.
Also, where can I find docs about the config?
@ricardokullock Rovo Dev CLI doesn’t let you hide or disable its built-in tools. Even if you deny them, the LLM still “sees” those tools and will try them first. Only MCP tools can be added—not replace defaults. The config isn’t public yet; the only docs are in the Rovo Dev CLI support pages. A feature request to allow disabling default tools is the right next step.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.