Env
Env manages named environment sets and the variables inside them.
What you do here
Section titled “What you do here”- switch between env sets
- create, rename, and delete env sets
- edit variable values, descriptions, and sensitivity
- import and export env data
Most common keys
Section titled “Most common keys”Normal mode
Section titled “Normal mode”j/k: move between env setse/Enter: open the variables tableCtrl+P: open the command palette
Variables table
Section titled “Variables table”j/k: move through rowsh/l: move betweenVariable,Value,Description, andSensitivee/Enter: edit the selected fielda: add a new variabled: delete the selected variableEsc: return to normal Env browsing
Field editing
Section titled “Field editing”Enter: saveEsc: cancelTab: placeholder completionCtrl+V: paste
Sensitive toggles directly. It does not open a text editor.
Common commands
Section titled “Common commands”homeenvhistorynew NAMErename NAMEimport PATHexport PATHset KEY=valuedeldel KEYedit
Quick examples
Section titled “Quick examples”Create a new env set
Section titled “Create a new env set”Use new NAME.
Add or change a variable
Section titled “Add or change a variable”Use either:
set KEY=value- interactive editing with
e, thenEnter
Import env data
Section titled “Import env data”Use import PATH.
Imported env data creates new env set(s). It does not merge into the currently selected env set.
Current import and export commands are key/value oriented:
.env-style files map cleanly to one env set- JSON env workspaces can be imported, but only key/value pairs are preserved
DescriptionandSensitivemetadata are part of app storage, not.envexport files
Placeholder workflow
Section titled “Placeholder workflow”Env values are intended to be consumed by placeholders inside requests. Inline editors and the raw body editor support placeholder completion with Tab.
Use placeholders like {{API_URL}} or {{TOKEN}} in request fields.
For full command behavior, see Command Palette.