Fix: Workspace-specific API configurations to prevent mixing between projects

[roomote]

Summary

Fixes #9071 - API configurations getting mixed up when using Roo Code in multiple VSCode projects simultaneously.

Problem

Previously, API configurations were stored globally using a fixed key "roo_cline_config_api_config" in VSCode's secrets storage. This caused all open VSCode instances to share the same configuration state, leading to:

• Incorrect API models being selected across different projects
• Context window sizes showing incorrect values (e.g., 1.0M for models that don't support it)
• Configuration changes in one project affecting all other open projects

Solution

Implemented workspace-specific storage for API configurations:

• Workspace Isolation: Each workspace now gets its own unique storage key based on a SHA256 hash of the workspace path
• Storage Key Format: roo_cline_config_ws_${workspaceHash} for workspace scenarios
• Fallback Support: Falls back to global storage when no workspace is open (e.g., standalone files)
• Automatic Migration: Existing global configurations are automatically migrated to workspace-specific storage on first load
• Backward Compatibility: Global configurations are preserved (not deleted) to maintain compatibility with other workspaces

Changes

src/core/config/ProviderSettingsManager.ts

• Added getWorkspaceIdentifier() method to generate unique workspace IDs
• Modified secretsKey getter to use workspace-specific keys when available
• Updated load() method to handle migration from global to workspace-specific storage
• Added workspaceId property to store the current workspace identifier

src/core/config/__tests__/ProviderSettingsManager.spec.ts

• Added comprehensive tests for workspace-specific storage
• Added tests for migration from global to workspace-specific configs
• Added tests for maintaining separate configs across workspaces
• Fixed import statements to use proper ES6 module syntax

Testing

All tests pass successfully:

✓ 44 tests passed
✓ No regressions in existing functionality
✓ New workspace isolation tests passing

Known Limitations

If the same workspace is opened from different file system paths (e.g., via symlinks or different mount points), it will create separate configurations. This is acceptable behavior as they're technically different paths.

Review Confidence

85% (High) - The implementation:

• ✅ Fully addresses the reported issue
• ✅ Maintains backward compatibility
• ✅ Includes comprehensive test coverage
• ✅ Follows project conventions and patterns
• ✅ Preserves security (continues using VSCode secrets storage)

Verification Steps

1. Open two different VSCode projects with Roo Code extension
2. Set different API configurations in each project
3. Verify that each project maintains its own configuration
4. Run tasks in both projects and confirm correct models are used
5. Close and reopen projects to verify persistence

---

Important

Implements workspace-specific API configuration storage in ProviderSettingsManager to prevent configuration mixing across VSCode projects.

• Behavior:
  • Implements workspace-specific storage for API configurations in ProviderSettingsManager.
  • Uses SHA256 hash of workspace path for unique storage keys.
  • Falls back to global storage when no workspace is open.
  • Automatically migrates existing global configurations to workspace-specific storage.
• Testing:
  • Adds tests in ProviderSettingsManager.spec.ts for workspace-specific storage and migration.
  • Tests for maintaining separate configurations across workspaces.
  • Tests for migration from global to workspace-specific storage.
• Misc:
  • Updates getWorkspaceIdentifier() to generate unique workspace IDs.
  • Modifies secretsKey getter to use workspace-specific keys.

^{This description was created by for 2688612. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Rooviewer   See task on Roo Cloud

Review completed. No issues found.

This PR correctly implements workspace-specific API configuration storage to prevent mixing between multiple VSCode projects. The implementation properly uses SHA256 hashing of workspace paths, includes automatic migration from global storage, maintains backward compatibility, and has comprehensive test coverage.

_{Mention @roomote in a comment to trigger your PR Fixer agent and make changes to this pull request.}