[BUG] Using Roo Code from multiple projects at the same time causes problem

[tapir]

Problem (one or two sentences)

Global Roo Code state causes confusion

Context (who is affected and when)

I had 2 different VSCode projects open, in one of them I've created a new API config with the model GLM (openrouter), selected it and started a task, while the task was running, in the second project I've created a new API config with Kimi K2 and started another task. I've noticed while both projects were working, the context window for both tasks became 1.0M which is impossible since none of these models support that and by the end of the tasks, in both projects, Claude (which is my default API config) was selected.

Reproduction steps

Open up 2 different VSCode projects.
In project one: create a new API configuration with model X. Run a YOLO long running task.
In project two: create another API configuration with model Y. Run a YOLO long running task.

Expected result

Both tasks starts and ends with their respective seleced new API configs

Actual result

API config selected gets mixed up

Variations tried (optional)

No response

App Version

v3.30.2

API Provider (optional)

OpenRouter

Model Used (optional)

GLM 4.6 and Kimi K2

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I'm exploring a potential fix for this issue where API configurations get mixed up between multiple VSCode projects. I'll investigate the state management and create a PR to share progress.

[roomote]

I've opened PR #9073 to address this issue: #9073

The fix implements workspace-specific API configuration storage to prevent mixing between multiple VSCode projects. Each workspace now maintains its own isolated configuration using a unique storage key based on a hash of the workspace path.

Key changes:

• Added workspace-specific storage keys based on SHA256 hash of workspace path
• Implemented automatic migration from global to workspace-specific storage
• Maintained backward compatibility for non-workspace scenarios
• Added comprehensive test coverage for the new functionality

All tests are passing locally and CI checks are currently running on the PR. Feedback and review are welcome!

[daniel-lxs]

Thanks for raising this! We're aware of the underlying limitation here, and we are exploring possible approaches to improve how Roo Code behaves across multiple open workspaces. That said, this isn’t something that’s currently planned or high priority for us, as it would require broader changes to how settings and state are managed.

We’ll keep this on our radar and update the issue if our plans change.