-
Notifications
You must be signed in to change notification settings - Fork 131
feat(workspace): add rootResolution setting for multi-root workspaces #538
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
Changes from all commits
b8f5058
93543b8
d21399c
d647011
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Without an explicit
"scope"this defaults to"window", which means a committed.vscode/settings.jsoncan override it. Since this setting controls which workspace folder is used to locate.roo/mcp.json(and therefore which MCP servers get registered), could a malicious workspace settings file redirect that to an attacker-controlled folder in a multi-root workspace?If workspace-level override should be blocked,
"scope": "machine"would prevent it. If it is intentional, worth documenting the trust decision here.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch — this setting feeds MCP-server discovery, so I've set
"scope": "machine"to prevent a committed workspacesettings.jsonfrom redirecting the resolved root. This intentionally disallows workspace-level overrides (the security tradeoff is deliberate).