tengu_ccr_upload_hold_marker
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.267, including the newest one read.
New telemetry gate can add upload-hold details to Claude Code Remote's upload data
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.267.
In the changelogs
10Releases whose published page names tengu_ccr_upload_hold_marker.
-
v2.1.318
Remote sessions get new timing options for sending held output
Remote sessions gain two settings, refreshed from the server, for when streamed output is sent and how long held output waits
gate cited by this entry
-
v2.1.315
Remote sessions rework how they keep their output in order
The part of Claude Code that runs remote sessions now tracks owed output rows and display hooks, and its old first-idle wait was removed
gate cited by this entry
-
v2.1.311
Remote sessions always follow the event policy the server sends
A remote switch for holding back remote-session events is gone, and remote sessions now always follow the event policy the server serves
gate cited by this entry
-
v2.1.311
Event holding in remote sessions can no longer be switched off remotely
Remote sessions now always hold and merge events, and the server-side switch that could turn this off is gone
gate cited by this entry
-
v2.1.305
New
CLAUDE_CODE_CCR_EVENT_FLUSH_POLICYsetting for remote sessionsA new environment variable,
CLAUDE_CODE_CCR_EVENT_FLUSH_POLICY, sets how a remote session sends out its eventsgate cited by this entry
-
v2.1.296
Remote sessions drop oversized event messages, and the preview tunnel tracks unanswered pings
Hosted remote sessions now drop event messages with too many fields, and the preview tunnel can reconnect after a run of missed pings
gate cited by this entry
-
v2.1.290
Remote sessions can now turn away apps on devices that fall below a trust policy
Remote sessions now check attached apps against a device trust policy and refuse ones that fall below it
gate cited by this entry
-
v2.1.288
Remote sessions can send their events over a continuous stream when the server offers one
Cloud session workers can now accept a server offer to send events over a streaming connection, alongside the usual one-request-per-batch route
gate cited by this entry
-
v2.1.286
Remote session startup records get a timestamp and a writer list
Startup requests in remote sessions now carry a creation time and a list of stream writers, and the remote client can react when the process exits
gate cited by this entry
-
v2.1.267
New CCR telemetry gate: upload hold marker
New telemetry gate can add upload-hold details to Claude Code Remote's upload data
gate cited by this entry
Gate readings
9| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.318 read on another version | Not enough to say | no value returned | no value returned | off |
| v2.1.315 read on another version | Not enough to say | no value returned | no value returned | off |
| v2.1.311 read on another version | Not enough to say | no value returned | no value returned | off |
| v2.1.305 read on another version | Not enough to say | no value returned | no value returned | off |
| v2.1.296 read on another version | Not enough to say | no value returned | no value returned | off |
| v2.1.290 read on another version | Not enough to say | no value returned | no value returned | off |
| v2.1.288 read on another version | Not enough to say | no value returned | no value returned | off |
| v2.1.286 read on another version | Not enough to say | no value returned | no value returned | off |
| v2.1.267 | Not enough to say | no value returned | no value returned | off |
Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.
First cited
1The earliest release whose published evidence quoted tengu_ccr_upload_hold_marker was v2.1.267, 9 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
1Build by build
49One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.