MCP tool "always allow" checkbox does not persist

[joshuacc]

App Version

3.11.14

API Provider

OpenRouter

Model Used

Gemini 2.5 Pro

Actual vs. Expected Behavior

I have a Github MCP server set up. When Roo needs to use it, it correctly prompts, asking for permission. I click the "Always allow" checkbox. But after hitting the "Approve" button, the checkbox state reverts to unchecked.

So I have to manually approve every time Roo tries to look up issue details on Github.

Detailed Steps to Reproduce

1. Set up an MCP server
2. In settings, auto-approve MCP use in general
3. Trigger Roo to use the MCP server
4. When Roo asks for permission to use the tool, check "always allow"
5. Click "approve"
6. Observe that the "always allow" checkbox is now unchecked.
7. Repeat steps 2 & 3. Observe that the checkbox is unchecked.

Relevant API Request Output

Additional Context

No response

[dosubot]

Hello @joshuacc! I'm Dosu, a bot here to help you with bugs, answer your questions, and assist you in becoming a contributor. I'll be here while you wait for a human maintainer. How can I assist you today?

The issue you're experiencing with the "always allow" checkbox not persisting could be due to several reasons, but unfortunately, I couldn't find specific information in the codebase or documentation about how the state of this checkbox is managed or stored. There might be a bug or a missing feature related to persisting the checkbox state across sessions.

Here are a few steps you can take to troubleshoot or report this issue:

1. Check for Known Issues: Look for any open issues in the Roo-Code repository that might relate to this problem. There might be ongoing discussions or fixes in progress.

2. Submit a Bug Report: If you don't find any related issues, consider submitting a detailed bug report to the repository. Include the steps to reproduce the issue, as you've outlined, and any other relevant information.

3. Review Recent Changes: Check the recent commits or changes in the codebase related to MCP tool's permission handling or UI components. There might be updates or fixes that address this issue.

4. Error Handling and Logging: If possible, enable any logging or error handling features in the application to see if there are any errors being logged when the checkbox state fails to persist.

These steps can help identify whether this is a known issue or if further investigation is needed.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[hannesrudolph]

@joshuacc cannot repro. Do you have multiple instances of Roo Code open in the same workspace or any other factors which might give us a hint as to why this behaviour is not working in your situation?

[joshuacc]

I'm not using multiple instances in the same workspace. I am using VS Code on Windows. My code is in WSL with Roo installed inside WSL. Not sure if that would have any effect, though.

And for the record, I've update the extension to the latest version. Still have the same problem.

[hannesrudolph]

I have personally had this happen but it is intermittent. Frustrating. I think it has to do with the way the mcp process is shared between instanced in my case. @joshuacc in your case is it consistent or intermittent?

[joshuacc]

For me it is consistent. The always allow checkbox has never worked for me.

[adgower]

always allow is not working for me also cursor, windows 11

[h5kk]

you have multiple instances of Roo Code open in the same workspace or any other factors which might give us a hint as to why this behaviour is not working in your situation?

I'm having the same issue using:
Workspace/VSCode Instance 1: /FolderForWorkspace1/
Workspace/VSCode Instance 1: /FolderForWorkspace2/