{"version":"2.1.310","anchor":"env-var-tracking-in-settings-env-application-records-and-res","canonical_anchor":"env-var-tracking-in-settings-env-application-records-and-res","heading":"Environment variables from settings can now remember the value they replaced","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/env-var-tracking-in-settings-env-application-records-and-res","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Environment variables from settings can now remember the value they replaced\n\nWhen settings set environment variables, Claude Code can now record each variable's earlier value so it can be put back later\n\n**Unclear.** It is not clear when this recording is used, so it is unclear whether removing a variable from your settings now restores its old value.\n\n**What**\n\nYour settings can set environment variables, which are named values passed to programs. When Claude Code applies them, it can now record the value a variable had before it was overwritten, so that value can be put back later.\n\n**Why**\n\nThis suggests that environment variables from settings can be undone when settings reload.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}