Slash commands stored in wrong folder

[kfuglsang]

App Version

v3.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 folder in which slash commands should be stored. It simply creates .roo\commands within the first folder in the multi-root 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).

💥 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.

📄 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. I'll investigate the problem with slash commands being stored in the wrong folder in multi-root workspaces and work on a solution. Thanks for the clear reproduction steps!

[roomote]

I have submitted a pull request to fix this issue: #6701

The fix adds a new utility function findWorkspaceWithRoo() that searches through all workspace folders to find the one containing the .roo directory, ensuring slash commands are created in the correct location in multi-root workspaces.

The PR is currently undergoing automated checks.

[kfuglsang]

The issue seems to be more general than just slash commands.
Roo code also does not identify the mcp servers that exist in the .roo\mcp.json file. If I use the UI to add a MCP from the marketplace, this creates a new file in the first directory, i.e. .docs\.roo\mcp.json