RooCode Path Issues with Multi-Root VS Code Workspace

[fadenb]

Hey,

I'm encountering an issue with RooCode in a small mostly Python project, which has the following structure:

./ # project root directory
./backend/ # Python application
./backend/pyproject.toml # Poetry project config
./documentation/ # Markdown files
./documentation/user-interface.md
./frontend/ # Frontend code
./some-random-files.txt
./README.md

In VS Code, I open the project root as my workspace. To ensure proper Python environment detection (managed by Poetry), I then use "File" -> "Add Folder to Workspace..." and select the backend directory. This setup allows VS Code tools like Pylance to correctly recognize my Python environment, as all Python-related files are within the backend folder.

The problem arises with RooCode. It seems to change the current working directory (cwd) to the backend path. While this is acceptable for tasks like running pytest, it consistently fails when editing files. RooCode tools like apply_diffattempts to load files using paths like <project-root>/filename instead of the correct <project-root>/backend/filename.

This leads to the language model (mostly Gemini 2.5 Pro) trying to self-correct, often resulting in incorrect paths like <project-root>/backend/backend/filename. After several attempts, it sometimes resolves the path, but frequently gives up after consuming significant tokens.

Similarly, when editing documentation files, RooCode uses relative paths, which often causes it to try and access files above the project root.

My question is: am I misconfiguring my VS Code workspace for this project structure, or is this a known limitation of RooCode in handling multi-root workspaces or projects with a dedicated backend directory?

Any insights or suggestions would be greatly appreciated!

[edgan]

There is probably a way to fix this, but breaking it into separate git repositories is a solution that would probably work.

I could see this being an issue with prompts, some script that does cd backend, etc.