Settings
Configure ENV Manager Pro in VS Code Settings (Ctrl+, / Cmd+,) by searching for ENV Manager.
Available Settings
envManagerPro.rotationDays
Type: number
Default: 90
The number of days after which a secret is considered stale. When you run Check Rotation, any variable not changed within this many days is flagged in the report.
"envManagerPro.rotationDays": 60
Planned Settings
The following settings are on the roadmap:
| Setting | Description |
|---|---|
envManagerPro.excludePatterns | Glob patterns for files to exclude from diagnostics |
envManagerPro.autoRevealOnSelect | Auto-reveal values when a file is selected |
envManagerPro.defaultExportFormat | Default CI/CD export format |
envManagerPro.syncTarget | Default cloud sync target (vercel / doppler / github) |
Where Tokens Are Stored
API tokens (Vercel, GitHub, Doppler, Infisical) are stored in VS Code SecretStorage, which delegates to the OS keychain:
- macOS — macOS Keychain
- Windows — Windows Credential Manager
- Linux — libsecret / GNOME Keyring
Tokens are stored under keys like envManager.vercelToken, envManager.githubToken, etc. To remove them, simply revoke the token at the provider and the extension will prompt for a new one on the next sync.
Workspace vs User Settings
All ENV Manager Pro settings can be set at the user level (global) or workspace level (per-project). Workspace settings take precedence, so you can set different rotation thresholds per project.