tengu_ccr_replay_acks_at_request_dispatch
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.280, including the newest one read.
A server setting used for one cloud session type was only renamed internally and still falls back to off
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.290.
In the changelogs
1Releases whose published page names tengu_ccr_replay_acks_at_request_dispatch.
-
v2.1.290
No change to a cloud session setting that stays off by default
A server setting used for one cloud session type was only renamed internally and still falls back to off
gate cited by this entry, found in this entry's text
Gate readings
1| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.290 read on another version | Off by default, switched on for this account | on | on | 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.
Flag server, over time
4| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| this account | on | 2026-09-23T15:35:05Z | 2026-10-09T01:05:07Z | v2.1.280 to v2.1.295 |
| anonymous | on | 2026-09-23T15:30:05Z | 2026-10-09T01:05:07Z | v2.1.280 to v2.1.295 |
| this account | off | 2026-09-23T15:00:07Z | 2026-09-23T15:30:05Z | v2.1.280 |
| anonymous | off | 2026-09-23T12:50:04Z | 2026-09-23T15:25:04Z | v2.1.280 |
One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.
First cited
1The earliest release whose published evidence quoted tengu_ccr_replay_acks_at_request_dispatch was v2.1.290, 5 Oct 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
16One 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.