{"version":"2.1.169","anchor":"job-persistence-security-non-allowlisted-keys-stripped-on-lo","canonical_anchor":"job-persistence-security-non-allowlisted-keys-stripped-on-lo","heading":"Job Persistence Security: Non-Allowlisted Keys Stripped on Load","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.169\/e\/job-persistence-security-non-allowlisted-keys-stripped-on-lo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.169","markdown":"### Job Persistence Security: Non-Allowlisted Keys Stripped on Load\n\n**What**\n\nWhen Claude Code resumes a persisted background job, it now strips any `providerEnv` keys or `respawnFlags` tokens from the saved state that are not on the internal allowlist. This prevents unintended environment leakage from older or externally-modified job state.\n\n**Details**\n\n- A warning is logged when stripping occurs: `[jobs] stripped non-allowlisted providerEnv key(s) from persisted job state`\n- Duplicate `respawnFlags` tokens (same flag specified multiple times) are also deduplicated \u2014 the last occurrence wins for flags that take a value\n- Behavior is transparent to users; jobs continue to resume normally\n\n**Evidence**\n\nJob state sanitizer (search for `\"[jobs] stripped non-allowlisted providerEnv key(s)\"`) \u2014 `nY7()` and `XXH()` at line ~219333"}