SASVA Settings Not Syncing Across VS Code Profiles or Workspaces
Problem
SASVA extension settings configured on one machine, VS Code profile, or workspace (such as selected model, auto-approve preferences, or custom server configuration) do not appear when the same user opens SASVA in a different VS Code profile, a different workspace, or a second machine. The user has to reconfigure SASVA from scratch each time.
Symptoms
- Model selection, auto-approve toggle, or other SASVA preferences revert to defaults in a new VS Code profile or new workspace.
- Settings configured on a work laptop do not appear when the same user signs in to SASVA on a second machine.
- Using VS Code's built-in Settings Sync does not carry over SASVA-specific preferences, even though other extension settings sync correctly.
Root Cause
SASVA stores some of its configuration at the workspace level (tied to the specific folder/workspace opened in VS Code) rather than at the user/global level. VS Code Profiles and Settings Sync only sync settings that are registered under VS Code's global "user settings" scope; workspace-scoped SASVA settings (stored in .vscode/settings.json of that specific project, or in workspace storage) are intentionally excluded and must be set per workspace.
Separately, some SASVA preferences are tied to the authenticated account/session on the server side rather than the local extension, and will only "sync" once the user signs in on the new machine/profile — they do not transfer via VS Code's local settings sync mechanism at all.
Resolution/Workaround
For workspace-level settings
- Check if the setting was applied at the workspace level: open Settings (Ctrl+, / Cmd+,), switch to the Workspace tab, and search for the SASVA setting.
- If found there, either re-apply it in each workspace, or move the setting to the User tab so it applies globally across all workspaces.
- For teams, commit a shared .vscode/settings.json with the desired SASVA workspace settings to the repository so every workspace clone inherits the same configuration automatically.
For account/server-side preferences
- Sign in to SASVA on the new machine/profile using the same account.
- Reload the VS Code window after sign-in to force a fresh configuration fetch from the server.
- Re-select the desired model/role if it does not appear automatically — this is a one-time step per new machine/profile, not a recurring issue.
Escalation
If a setting that should be account-level (e.g., model role assignment) still does not appear after sign-in and window reload on the new machine, contact sasva_support_in@persistent.com with both machine/profile names and the specific setting affected.
Comments