docs/tutorials/environment-variable-sets

Intermediate10 minFree (local) · Pro (sync)

Environment variable sets

Named env groups locally. Pro syncs env sets to the cloud.

Free vs Pro

Free: create named env sets in the VS Code extension or edit ~/.recall/env.json. Soft cap ~50. CLI recall env … still requires login. Pro syncs env sets with the cloud. Don't put production secrets in plain local files without encryption.

01Free: create an env set in VS Code

In VS Code open recall → Env → create. Name it staging and add variables such as:

DB_HOST=staging-db.company.comAPI_KEY=sk-staging-abc123

Stored in ~/.recall/env.json. No account needed.

02Pro: CLI env sets (login required)

After login on Pro/Team, save and load env sets from the terminal:

recall env save staging? Variable name: DB_HOST? Value: staging-db.company.com? Variable name: API_KEY? Value: sk-staging-abc123? Variable name: (empty to finish)✔ Saved env set "staging" with 2 variableseval $(recall env use staging)echo $DB_HOST # staging-db.company.comrecall env listrecall env show stagingrecall sync

// what's next

→ Use snippets for deployment scripts → Integrate recall with CI/CD pipelines