[BUG] RooCode Settings Import Fails in Code-Server Environment

[benzntech]

Problem (one or two sentences)

RooCode extension cannot import settings from backup files when running in code-server, preventing users from migrating their configurations from VS Code Desktop to remote code-server environments.

Context (who is affected and when)

Affects users who want to use RooCode in code-server (browser-based VS Code) and need to import their existing provider profiles, API configurations, and global settings from VS Code Desktop installations.

Reproduction steps

Affects users who want to use RooCode in code-server (browser-based VS Code) and need to import their existing provider profiles, API configurations, and global settings from VS Code Desktop installations.

Reproduction steps

1. Environment/setup:

   • macOS 14+, code-server v4.104.2, RooCode v3.28.15 (rooveterinaryinc.roo-cline)
   • Have existing RooCode settings backup file from VS Code Desktop
   • Install RooCode extension in code-server

2. Exact actions:

   • Access RooCode settings/preferences in code-server
   • Attempt to use built-in import functionality
   • Try placing backup file in various expected locations
   • Restart code-server to trigger auto-import
   • Check extension logs for import status

3. What you observed after each step:

   • Import functionality appears non-functional
   • Extension logs show: [AutoImport] No auto-import settings path specified, skipping auto-import
   • Provider profiles and global settings remain empty
   • Only manual file copying of MCP settings works partially

Expected result

RooCode should successfully import complete settings from backup files including provider profiles (API keys, model configurations), global settings (custom instructions, permissions), and all user preferences.

Actual result

Settings import fails completely. Extension shows empty configuration with no provider profiles, API settings, or global preferences. Manual file copying only works for MCP settings and custom modes, but core settings remain missing.

Variations tried (optional)

Tried manual file operations, different restart sequences, placing backup files in multiple storage locations, and checking both VS Code and code-server storage paths. Only partial success with manual copying of specific files.

App Version

v3.28.15

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

N/A

Relevant logs or errors (optional)

roo-cline extension activated - {"publisher":"RooVeterinaryInc","name":"roo-cline","version":"3.28.15"}
[Default Commands Migration] Migration already completed, skipping
Skipping migration of cline_custom_modes.json to custom_modes.json: old file not found
Skipping migration of cline_mcp_settings.json to mcp_settings.json: old file not found
No custom_modes.json found, skipping YAML migration
CloudService not ready, deferring cloud profile sync
[auth] Using WebAuthService
[auth] changeState: initializing -> logged-out
[AutoImport] No auto-import settings path specified, skipping auto-import

**Storage Location Analysis:**
- VS Code Desktop storage: `/Library/Application Support/Code/User/globalStorage/rooveterinaryinc.roo-cline/`
- Code-server storage: `~/.local/share/code-server/User/globalStorage/rooveterinaryinc.roo-cline/`
- Backup file structure contains `providerProfiles`, `globalSettings`, and other core configurations that aren't being imported

**Impact:** Users cannot migrate from VS Code Desktop to code-server, requiring complete manual reconfiguration of all RooCode settings, which is time-consuming and error-prone.

I'm exploring a potential fix for the settings import issue in code-server environments. I'll investigate why the auto-import is being skipped and work on enabling proper migration of provider profiles and global settings from VS Code Desktop to code-server.

[daniel-lxs]

Thanks for reporting this! We really appreciate you taking the time to detail the issue and environment. At the moment, our focus is on ensuring a stable release for VS Code Desktop, and code-server environments aren’t part of our supported targets.

We’re marking this as not planned for now, but your report helps us track interest in potential future compatibility. Thanks again for your contribution and understanding!