BUG: Diff editing & read paths are incorrect for multi-folder/repo vscode workspaces

[bitnom]

Which version of the app are you using?

3.10.5

Which API Provider are you using?

Google Gemini

Which Model are you using?

gemini pro 2.5

What happened?

you'll get something like:

Error applying diff:
ENOENT: no such file or directory, open '/home/user/code/workspace/package.json'

and then:

Error reading file:
File not found: /home/user/code/workspace/libs/mcp-typescript-sdk/libs/mcp-typescript-sdk/package.json

(notice path duplication)

where /home/user/code/workspace/libs/mcp-typescript-sdk is the git repo it's supposed to be working on.

Steps to reproduce

Create a multifolder vscode workspace with multiple git repos and prompt roo to start working on one of the subdir projects. I tried to resolve it by global prompt explaining the situation about CWD but it didn't work.

Relevant API REQUEST output

Additional context

This problem applies to both reading files and editing them. After a few tries the AI is usually able to read the file by adjusting paths. The solution the AI is sometimes able to come up with for editing is to write out the entire file without diff editing. Idk why. I'm guessing that tool is handling paths differently. It's never able to recover diff editing from what I've seen.

[hannesrudolph]

@mrubens @samhvw8 Roo does not support multip workspace setups yet, correct?

[EricAtORS]

I'm having the same issue.
It was working in the past. I didn't have time to use Roo much in the past few weeks, so I can't tell when it started happening.

In VSCode, you can add multiple folders to a single workspace (File > Add Folder to Workspace ...).

Here's the "log" (not sure what to call it) from trying to apply a diff:

[apply_diff for 'Data Organizer Standalone/OrsDataOrganizer_c8d5b3a2586e11e8a722448a5bd787f8/projectform.py'] Result:

The tool execution failed with the following error:
<error>
Error applying diff: {"errno":-2,"code":"ENOENT","syscall":"open","path":"/home/eric/git/comet/YUL-Data-Organizer/Data Organizer Standalone/OrsDataOrganizer_c8d5b3a2586e11e8a722448a5bd787f8/projectform.py","name":"Error","message":"ENOENT: no such file or directory, open '/home/eric/git/comet/YUL-Data-Organizer/Data Organizer Standalone/OrsDataOrganizer_c8d5b3a2586e11e8a722448a5bd787f8/projectform.py'","stack":"Error: ENOENT: no such file or directory, open '/home/eric/git/comet/YUL-Data-Organizer/Data Organizer Standalone/OrsDataOrganizer_c8d5b3a2586e11e8a722448a5bd787f8/projectform.py'\n\tat async open (node:internal/fs/promises:639:25)\n\tat async Object.readFile (node:internal/fs/promises:1242:14)\n\tat async Pwe.open (/home/eric/.vscode-server/extensions/rooveterinaryinc.roo-cline-3.11.4/dist/extension.js:1091:715)\n\tat async a4n (/home/eric/.vscode-server/extensions/rooveterinaryinc.roo-cline-3.11.4/dist/extension.js:2982:173)\n\tat async t.presentAssistantMessage (/home/eric/.vscode-server/extensions/rooveterinaryinc.roo-cline-3.11.4/dist/extension.js:3110:635)"}
</error>

<environment_details>
# VSCode Visible Files
Data Organizer Standalone/OrsDataOrganizer_c8d5b3a2586e11e8a722448a5bd787f8/projectitemwidget.py

# VSCode Open Tabs
Data Organizer Standalone/OrsDataOrganizer_c8d5b3a2586e11e8a722448a5bd787f8/project_item_context_menu.py,Data Organizer Standalone/OrsDataOrganizer_c8d5b3a2586e11e8a722448a5bd787f8/projectitemwidget.py

# Current Time
2025-04-03, 1:15:55 p.m. (America/Vancouver, UTC-7:00)

# Current Context Size (Tokens)
81,978 (41%)

# Current Cost
$1.34

# Current Mode
<slug>code</slug>
<name>Code</name>
</environment_details>

The issue is that the path exists, but the path Data Organizer Standalone/OrsDataOrganizer_c8d5b3a2586e11e8a722448a5bd787f8/projectform.py is relative to one of the folders I've added, not the first one that is defined in .code-workspace file.

[EricAtORS]

I tried to dig into it, but I'm not sure how to setup the debug environment.

Anyways, looking at the changes.
I've narrowed it down to this:

https://github.com/RooVetGit/Roo-Code/blob/065c5ab222419fe8105b134d8b45e899454b8dc5/src/utils/path.ts#L112,L115

It would seem like prior to this commit, everyfile was always relative to cwdPath , but with the change to support multiple workspaces, that line of code breaks that assumption and all the call sites are not updated to reflect this change.

@bitnom
One temporary solution that I found that sort of works is to have files from different folders opened and that seemed to resolve my issue. I'll be trying it some more tomorrow.

[samhvw8]

@EricAtORS you can use mise ( https://mise.jdx.dev/getting-started.html) setup env and contribute, we don't have support multiple folder in 1 workspace yet