Follow Discord
Sweep 29 Sep 2026 · 18:10Z Build v2.1.285 506 read Stable v2.1.280 Latest v2.1.285 Next v2.1.285 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

worker_epoch parse bug fixed in RegisterWorker

Fixed a bug where the daemon read a worker's epoch number from the wrong place, producing garbage values

Under the hood Bug Fixes
JSON All of v2.1.280
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
DaemonArea: what it touches
Bug FixesKind: in v2.1.280,
Bug FixesSection of the release
What

When the Claude Code daemon (a background process) registers a worker, it reads back a value called worker_epoch from the response. This code was pulling that value from the wrong variable, so it was parsing a value that didn't actually hold the epoch number. This has been fixed so worker_epoch is now read from the correct response object.

Why

Before this fix, worker_epoch would have come out as NaN or some other garbage value instead of the real number, since the code was reading it from the wrong place. That could confuse any logic that depends on tracking a worker's epoch correctly.

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 doubtThe finding doesn't say what worker_epoch is used for downstream, so the practical impact of the garbage value is inferred only generally.

See this entry in the whole of v2.1.280 →

Feedback