8000 MCP tool "always allow" checkbox does not persist · Issue #2568 · RooVetGit/Roo-Code · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

MCP tool "always allow" checkbox does not persist #2568

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
joshuacc opened this issue Apr 13, 2025 · 12 comments
Open

MCP tool "always allow" checkbox does not persist #2568

joshuacc opened this issue Apr 13, 2025 · 12 comments
Labels
bug Something isn't working needs scoping Needs up-front scoping to be actionable

Comments

@joshuacc
Copy link

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

@joshuacc joshuacc added the bug Something isn't working label Apr 13, 2025
Copy link
dosubot bot commented Apr 13, 2025

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
Copy link
Collaborator

@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?

@hannesrudolph hannesrudolph moved this from New to Issue [Needs Info] in Roo Code Roadmap Apr 15, 2025
@joshuacc
Copy link
Author
joshuacc commented Apr 16, 2025

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 hannesrudolph added the needs information Needs more information to be actionable label Apr 17, 2025
@hannesrudolph
Copy link
Collaborator
hannesrudolph commented Apr 23, 2025

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?

@hannesrudolph hannesrudolph moved this from Issue [Needs Info] to Issue [Needs Scoping] in Roo Code Roadmap Apr 23, 2025
@joshuacc
Copy link
Author

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

@adgower
Copy link
adgower commented Apr 23, 2025

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

@h5kk
Copy link
h5kk commented Apr 26, 2025

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/

@hannesrudolph hannesrudolph added needs scoping Needs up-front scoping to be actionable and removed needs information Needs more information to be actionable labels Apr 28, 2025
@robertheadley
Copy link

Also experiencing issues with this. It has been persistent for a while, though I recall it working at one point.

@Sumpfgulasch
Copy link

having the same issue with MCP commands of a Unity MCP server. As soon as I scroll through the chat, the checkbox of the individual "always allow" checkbox is deselected. The one for "Auto-approve" always stays.

@niksite
Copy link
niksite commented May 2, 2025

I noticed that the command checkbox states in the MCP Servers settings are immediately reflected in the ~/.roo/mcp.json file. However, the always allow checkbox in the chat does not update this file.

Is this because the chat setting doesn't expect a project-specific mcp.json file?

@moga111
Copy link
moga111 commented May 6, 2025

Same here, only way when the MCP is active I have to keep approving, the "Always allow" is not working.

@Nolson37
Copy link
Nolson37 commented May 7, 2025

I'm having the exact same issue when it's interacting with an mcp server

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs scoping Needs up-front scoping to be actionable
Projects
Status: Issue [Needs Scoping]
Development

No branches or pull requests

9 participants
0