{"version":"2.1.247","anchor":"cloud-sessions-can-report-which-worker-generation-they-are-o","canonical_anchor":"cloud-sessions-can-report-which-worker-generation-they-are-o","heading":"Cloud sessions can report which worker generation they are on","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/cloud-sessions-can-report-which-worker-generation-they-are-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Cloud sessions can report which worker generation they are on\n\nCloud sessions track which worker generation they're on and re-register only after a worker restart.\n\n**What**\n\nThe startup message a session sends can now carry a worker generation number, taken from `CLAUDE_CODE_WORKER_EPOCH`, which changes each time the session's cloud worker restarts. A `claude --cloud` client that has already acknowledged one generation re-registers its device hooks and tool announcements only when the number differs.\n\n**Details**\n\n- Optional field; emitted only on workers where the remote-tools gate `tengu_violin_wood` is on, and that gate falls back to off when no server value is present.\n\n**Evidence**\n\n`CLAUDE_CODE_WORKER_EPOCH`\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.247; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Cloud Sessions\n- Names: `CLAUDE_CODE_WORKER_EPOCH`, `--cloud`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}