[BUG] settings not exporting properly in VSCode

[IvanGarL]

Problem (one or two sentences)

I'm trying to export my RooCode extension settings into a json file but the file is not created and no error is reported by the extension in VSCode.

Context (who is affected and when)

I'm using a linux OS with a non up to date version of VSCode.

OS: Linux Ubuntu 24.04.3 LTS
VSCode version:

Version: 1.98.2
Commit: ddc367ed5c8936efe395cffeec279b04ffd7db78
Date: 2025-03-12T13:32:45.399Z
Electron: 34.2.0
ElectronBuildId: 11161602
Chromium: 132.0.6834.196
Node.js: 20.18.2
V8: 13.2.152.36-electron.0
OS: Linux x64 6.17.0-14-generic

RooCode extension:

Version: 3.51.1 (7c9722b)
Provider: OpenAI Compatible
API Provider: custom url with custom API Key

Reproduction steps

1. Open VSCode
2. Open Roo-code without a Roo account
3. Set up provider to be OpenAI compatible with custom Base URL and custom API Key (I'm using an OpenWebUI instance)
4. Try to export settings to json from the "About Roo Code" tab.

Expected result

json settings file is saved in the configured route (e.g ./Documents/roo-code-settings.json)

Actual result

No file is saved

Variations tried (optional)

No response

App Version

3.51.1

API Provider (optional)

OpenAI Compatible

Model Used (optional)

N/A

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote-v0]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause

The exportSettings function in src/core/config/importExport.ts has multiple silent failure paths with no user-facing feedback:

1. Silent catch block (line 281-283): When any error occurs during export (e.g. schema validation, file write failure), the error is only logged to console.error with a comment saying "the UI will handle showing error messages" -- but no message is actually sent to the UI.

2. Silent return on missing provider profiles (line 271-273): If providerSettingsManager.export() returns undefined, the function returns without creating a file or notifying the user.

3. Schema validation failure in ProviderSettingsManager.export(): The discriminatedProviderSettingsWithIdSchema.parse() call (line 525) uses strict .parse() which throws on unexpected fields. If a config has properties that don't match the discriminated schema exactly, the entire export throws -- and gets silently swallowed.

4. No success feedback: Even when export succeeds, the user receives no confirmation.

Proposed Fix

1. Add error feedback in exportSettings (src/core/config/importExport.ts):

   • Replace the silent console.error in the catch block with vscode.window.showErrorMessage() so the user sees what went wrong.
   • Add a user-facing message when provider profiles are undefined (e.g. "No provider profiles found to export").

2. Add success feedback: Show vscode.window.showInformationMessage() after a successful export with the file path.

3. Make schema parsing more resilient in ProviderSettingsManager.export() (src/core/config/ProviderSettingsManager.ts):

   • Use .safeParse() instead of .parse() for discriminatedProviderSettingsWithIdSchema at line 525, falling back to the original config (via providerSettingsWithIdSchema) if the discriminated parse fails. This prevents a single config's schema mismatch from breaking the entire export.

4. Add/update tests to cover:

   • Export error feedback is shown to the user
   • Export succeeds with a confirmation message
   • Schema parse failures for individual configs don't break the entire export

This approach fixes both the root cause (potential schema validation failure) and the symptom (no user feedback on any failure path).

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.