{"version":"2.1.317","anchor":"workerepoch-is-passed-in-more-worker-modes","canonical_anchor":"workerepoch-is-passed-in-more-worker-modes","heading":"CLAUDE_CODE_WORKER_EPOCH is passed along in more kinds of session","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/workerepoch-is-passed-in-more-worker-modes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### `CLAUDE_CODE_WORKER_EPOCH` is passed along in more kinds of session\n\nClaude Code now passes on the `CLAUDE_CODE_WORKER_EPOCH` value when either of two conditions holds, where before only one condition counted\n\n**Unclear.** Which kinds of session the two conditions cover is not stated, so it is unclear whether a given setup now picks up the value.\n\n**What**\n\nClaude Code reads the `CLAUDE_CODE_WORKER_EPOCH` environment variable, a setting that comes from the environment Claude Code is started in, and passes its value along as the worker epoch. It used to do this only when one particular condition held. It now does it when either of two conditions holds, so the value is carried through in more situations.\n\n**Why**\n\nThis concerns how remote and worker sessions keep track of their epoch value. If you set `CLAUDE_CODE_WORKER_EPOCH`, it now takes effect in more cases.\n\n- Area: Sessions\n- Names: `CLAUDE_CODE_WORKER_EPOCH`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}