Instances & Context
Multiple instances (profiles)
Work across DEV, QA and PROD without re-logging every time. Each login creates a named profile with its own folder and secrets.
Each Login to Instance creates a named profile that stores the URL, username, auth method and environment type; secrets (the Basic password or the OAuth tokens) live in VS Code SecretStorage (per profile).
- Switch instantly from the dedicated status bar item (or
SN Widget: Switch Instance Profile). It's color-coded by environment — red for PROD, amber for QA — so you always know where you're connected. - One picker does it all: switch, add a new instance, disconnect, or remove a profile. Switching invalidates caches and re-syncs IntelliSense for the new instance.
- Per-instance folders: pulled widgets go to
widgets/<instance>/<widget>(slug = subdomain), so environments never mix. The instance folder is created on first login.
Safety guards
- Cross-instance push is blocked. A push reuses the widget's
sys_id, so pushing to a different instance than it came from could overwrite the wrong record. This is a hard block — there is no override. (Widgets pulled before this version have no instance stamp and aren't blocked; they self-heal on the next pull.) - PROD pushes need confirmation. Pushing to a profile marked PROD requires an extra modal confirmation, and silent auto-sync never pushes to PROD without a manual confirm.
Upgrading from an earlier version?
Your existing login becomes a profile automatically, and widgets already in the flat
widgets/ folder are reorganized into per-instance subfolders on first activation — once, safely, never overwriting. Both layouts keep working throughout.