Skip to content

context-engine-uploader: persist profiles across local/remote without Settings Sync#84

Merged
voarsh2 merged 2 commits into
Context-Engine-AI:testfrom
voarsh2:vscode-persist-profiles
Dec 19, 2025
Merged

context-engine-uploader: persist profiles across local/remote without Settings Sync#84
voarsh2 merged 2 commits into
Context-Engine-AI:testfrom
voarsh2:vscode-persist-profiles

Conversation

@voarsh2

@voarsh2 voarsh2 commented Dec 18, 2025

Copy link
Copy Markdown
Contributor

Store profilesDb in VS Code user settings (inspect() to avoid schema-default masking).

Keep backwards-compat by loading legacy profiles.json and migrating forward.

Make saveProfilesDb async and await saves in wizards.

Opt-in profiles + activeProfileId to globalState sync when available.

Add TODO about migrating glmApiKey from settings.json to SecretStorage.

… Settings Sync

Store profilesDb in VS Code user settings (inspect() to avoid schema-default masking).
Keep backwards-compat by loading legacy profiles.json and migrating forward.
Make saveProfilesDb async and await saves in wizards.
Opt-in profiles + activeProfileId to globalState sync when available.
Add TODO about migrating glmApiKey from settings.json to SecretStorage.
Debounce restarts to avoid rapid toggles.
Only restart when uploader is already running (watchProcess set).
@voarsh2 voarsh2 merged commit 1fbae79 into Context-Engine-AI:test Dec 19, 2025
1 check passed
@voarsh2 voarsh2 deleted the vscode-persist-profiles branch December 19, 2025 03:15
m1rl0k pushed a commit that referenced this pull request Mar 1, 2026
context-engine-uploader: persist profiles across local/remote without Settings Sync
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants