{"version":"2.1.232","anchor":"worker-processes-no-longer-inherit-resume-state","canonical_anchor":"worker-processes-no-longer-inherit-resume-state","heading":"Worker processes no longer inherit resume state","tier":"notice","area":"Session Management","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/worker-processes-no-longer-inherit-resume-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Worker processes no longer inherit resume state\n\nChild worker processes no longer inherit your session id, resume prompt or auth handles.\n\n**What**\n\nSpawning a worker now blanks the inherited resume and session environment variables, so a child process cannot pick up the parent's resume prompt, session id or auth handles.\n\n**Details**\n\n- Cleared: `CLAUDE_CODE_RESUME_PROMPT`, `CLAUDE_CODE_RESUME_FROM_SESSION`, `CLAUDE_CODE_REMOTE_SESSION_ID`, `CLAUDE_SESSION_INGRESS_TOKEN_FILE`, `CLAUDE_CODE_WEBSOCKET_AUTH_FILE_DESCRIPTOR`, `CLAUDE_CODE_COWORK_FRAME_ARTIFACTS`.\n- `CLAUDE_CODE_RESUME_INTERRUPTED_TURN` is set to `1` only for relaunches after the first.\n\n**Evidence**\n\n`CLAUDE_CODE_RESUME_INTERRUPTED_TURN`\n\n- Area: Session Management\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}