Variables

Each context page lists every variable in the project with its status in that context: set, missing, or expired. Set or edit a value with the pencil. The trash icon unsets the value in this context or deletes the variable everywhere.

Every value is encrypted in the browser or CLI. We store ciphertext only.

A variable can have one tag, like secrets or config. The tag applies in every context. Variables are sorted by tag. Check one or more tags in the menu above the list to show only those. Select all and Unselect all are at the top of the menu. Click a tag in the list to show only that tag.

Add a tag when you add a variable, or open a variable and edit Tag (all contexts). Tags use lowercase letters, numbers and hyphens, up to 32 characters. Like variable names, tags are stored as plain text.

Tags are for sorting in the dashboard. run still starts your app with every variable in the context.

npx getmyenv ls                         # names by context, never values
npx getmyenv set API_KEY                # prompts, input hidden
npx getmyenv set LOG_LEVEL=debug -c staging
npx getmyenv unset OLD_KEY              # from the default context
npx getmyenv unset OLD_KEY --all        # delete the name everywhere

Production CLI is read-only. Set Production values in the dashboard.

A value can have an expiry date. After that date getmyenv stops providing it and run treats it as missing.

npx getmyenv set TRIAL_KEY=abc --expires 2026-12-31

Expiry and unset stop getmyenv from providing the value. The credential still works at its provider until you rotate it there.

getmyenv does not keep old values. A new value replaces the old ciphertext. For a copy, use Backups or npx getmyenv backup.

On Variables, Export can download a .env.example with names only. Recipients set their own values.