{"version":"2.1.296","anchor":"background-job-state-ignored-environment-entries-are-now-re","canonical_anchor":"background-job-state-ignored-environment-entries-are-now-re","heading":"Background jobs now say which saved environment entries they ignored and why","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/background-job-state-ignored-environment-entries-are-now-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Background jobs now say which saved environment entries they ignored and why\n\nWhen a background job loads its `state.json`, Claude Code now lists ignored environment entries with a reason for each\n\n**What**\n\nBackground sessions save their state in a `state.json` file, including some environment entries, which are named values that programs read. When Claude Code loads that file, it now lists the saved entries it does not keep, each with a reason, such as:\n\n- not kept for background sessions\n\n- only kept when set to a true value such as 1\n\nSome entries are also checked before being kept. Before, entries that were not allowed were removed with only a general note that some had been stripped.\n\n**Why**\n\nIf a background session is missing an environment value you expected, the log now says which one and why.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}