Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.317 ·

CLAUDE_CODE_WORKER_EPOCH is passed along in more kinds of session

Claude Code now passes on the CLAUDE_CODE_WORKER_EPOCH value when either of two conditions holds, where before only one condition counted

Under the hood No documentation found Internal Changes
JSON All of v2.1.317
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.317,
Internal ChangesSection of the release

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.

What

Claude 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.

Why

This 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.

Read from
Names in the bundleCLAUDE_CODE_WORKER_EPOCH
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich kinds of session the two conditions cover is not stated, so it is unclear whether a given setup now picks up the value.

See this entry in the whole of v2.1.317 →

Feedback