{"version":"2.1.281","anchor":"settings-env-change-no-longer-preserves-claude-code-repl-exp","canonical_anchor":"settings-env-change-no-longer-preserves-claude-code-repl-exp","heading":"Settings env change no longer preserves CLAUDE_CODE_REPL explicitly","tier":"internal","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/settings-env-change-no-longer-preserves-claude-code-repl-exp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Settings env change no longer preserves CLAUDE_CODE_REPL explicitly\n\nWhen settings.env changes, Claude Code reapplies config environment variables and no longer saves and restores CLAUDE_CODE_REPL itself\n\n**Unclear.** The finding does not say whether the new helper keeps `CLAUDE_CODE_REPL` intact.\n\n**What**\n\nEnvironment variables are named values that programs read from their surroundings. `settings.env` is the setting that lists extra ones for Claude Code. When `settings.env` changes while Claude Code is running, Claude Code now calls a helper that reapplies the environment variables from your config, plus one other step.\n\nThe explicit step that saved `CLAUDE_CODE_REPL` beforehand and restored it afterwards has been removed.\n\n**Why**\n\nEnvironment changes are now handled by reapplying the config as a whole rather than by protecting one variable by name. If you rely on `CLAUDE_CODE_REPL`, it is worth checking that it still has the value you expect after changing `settings.env` mid-session.\n\n- Area: Settings\n- Names: `settings.env`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}