What
The bridge connects a Claude Code session to a worker running in the cloud. A worker epoch is a number that tells newer workers apart from ones that have been replaced. Before, the /bridge request sent an empty body ({}).
- The
/bridgerequest can now sendexpected_epoch. - A 409 epoch conflict is handled through
onEpochConflict. A 409 is the server's reply when the request clashes with the worker's current state. - Connection failures are treated as temporary.
- A 403
sub_reasonis checked to be in snake_case (lowercase words joined by underscores) before it is passed on. - The description of the
worker_epochfield now says every claude-code-server worker sends it, whatever thetengu_violin_woodflag reads. Before, it said the field was sent only where that flag was on. - The
register_device_hooksmention is removed from that description.
Why
The bridge can now detect when it is talking to a worker that has been replaced and deal with it, rather than carrying on with an outdated one. The worker epoch is now described as always present, no longer tied to the tengu_violin_wood flag.
tengu_violin_wood Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.288: 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.
Read once, for one account on one subscription tier, against v2.1.288. It isn't a statement about your account. What a flag value here can and cannot tell you
It is not clear what supplies the expected epoch, so when it is actually sent is unknown.