A remote session's worker reports what is happening (its events) to the server. Until now it only did so by sending each batch of events as a separate request. It can now also send them over a continuous streaming connection, when the server offers one. The offer can come in the reply the worker receives at startup, or in its regular check-ins with the server.
Along with this:
- the worker sends a count of how many times the stream has broken
- its requests use their own set of network connections, kept apart from the rest of Claude Code
This applies when the process manages itself and is either not hosted, or is hosted in Anthropic's cloud.
This changes how events from a remote session reach the server, and what happens when the stream drops partway through. Nothing changes until the server starts sending offers.
tengu_ccr_event_hold_enabled Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.288: on
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.
tengu_ccr_upload_hold_marker Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · 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 known whether the server currently offers the streaming connection.