{"version":"2.1.280","anchor":"cloud-worker-reconnection-logic-tied-to-claude-code-worker-e","canonical_anchor":"cloud-worker-reconnection-logic-tied-to-claude-code-worker-e","heading":"Cloud worker reconnection logic tied to CLAUDE_CODE_WORKER_EPOCH","tier":"soon","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/cloud-worker-reconnection-logic-tied-to-claude-code-worker-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Cloud worker reconnection logic tied to CLAUDE_CODE_WORKER_EPOCH\n\nCloud worker reconnect prompts now gate on the worker generation number having advanced\n\n**Unclear.** Whether this is currently active for a given reader isn't settled: `tengu_violin_wood` read off for both this site's account and the anonymous baseline, but no reading has been taken under this release.\n\n**What**\n\nNew helper functions decide whether Claude Code should re-announce itself to a cloud\/remote worker or ask the user about reconnecting. They now check that `CLAUDE_CODE_WORKER_EPOCH` (the worker generation number) has advanced past 1, along with other session-state conditions, before prompting the user or computing how long to wait before reconnecting.\n\n**Why**\n\nThis refines when Claude Code decides a cloud session's worker has actually restarted and needs re-registration, building on the existing worker-generation tracking, so reconnect prompts and waits are triggered more accurately.\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.280; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cloud Sessions\n- Names: `CLAUDE_CODE_WORKER_EPOCH`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}