Roo does not identify .roo folder in multiroot workspace

[kfuglsang]

App Version

3.25.6

API Provider

Anthropic

Model Used

N/A

Roo Code Task Links (Optional)

No response

🔁 Steps to Reproduce

When working in a multi root workspace, Roo Code incorrectly identifies the .roo folder.
It simply places it in the top-most folder of the workspace.

Can easily be reproduced by using a workspace file like this:
{ "folders": [ { "name": ".docs", "path": ".docs" }, { "name": ".roo", "path": ".roo" }, { "name": "src", "path": "src" } ] }

If you create a new slash command (i.e. commit), it will create .docs\.roo\commands\commit.dk). Same thing happens if you modify the MCP servers in the project, which becomes .docs\.roo\mcp.json.

Supersedes issues #6700

💥 Outcome Summary

Expected slash commands to be stored in .roo\commands. Instead, it created .roo\commands as a subdirectory of the first folder in the workspace.

Expected mcp.json to be stored in .roo\mcp.json but was placed in .docs\.roo\mcp.json

📄 Relevant Logs or Errors (Optional)

[roomote]

Hi! I'm here to help out the maintainers and am going to see if I can fix this issue or at least get close enough to be helpful!

I see this is a broader issue than #6700 - it affects not just slash commands but also MCP server configuration and potentially other .roo folder operations in multi-root workspaces. I'll investigate and work on a comprehensive fix that ensures Roo Code correctly identifies and uses the .roo folder when it's one of the workspace folders.

Thanks for the clear reproduction steps and for identifying this broader scope!

[roomote]

✅ Fix implemented and PR created!

I've successfully implemented a fix for the issue where Roo Code incorrectly identifies the .roo folder location in multi-root workspaces.

Summary of changes:

• Added a new findWorkspaceWithRoo() utility function that checks if any workspace folder is named .roo
• Updated getProjectRooDirectoryForCwd() to use this new utility, ensuring it returns the workspace folder itself when it's named .roo
• Added comprehensive unit tests to verify the fix works correctly
• Updated all other files that were constructing .roo paths directly to use the vscode-aware wrapper functions

Pull Request: #6721

#6721

All CI checks have passed successfully! ✅

The fix ensures that when .roo is one of the workspace folders in a multi-root workspace, Roo Code will correctly identify it as the configuration directory instead of creating a nested .roo/.roo structure.

This should resolve the issue you were experiencing with your multi-root workspace setup.