{"version":"2.1.280","anchor":"provider-env-state-validated-against-saved-job-state","canonical_anchor":"provider-env-state-validated-against-saved-job-state","heading":"Provider env state validated against saved job state","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/provider-env-state-validated-against-saved-job-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Provider env state validated against saved job state\n\nRestored background-job provider environment variables are now validated, not just copied\n\n**What**\n\nWhen Claude Code restores the provider environment settings (`providerEnv`) from a saved background job's `state.json` file, it now runs those values through a validation and sanitization step, rather than copying them through unchanged.\n\n**Why**\n\nValidating restored environment data before reusing it guards against a saved job state being stale, malformed, or unsafe to apply directly.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}