tengu_ccr_handoff_metadata
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.242, including the newest one read.
Handing a session to the cloud can include a snapshot of your checkout, off by default.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.242.
In the changelogs
4Releases whose published page names tengu_ccr_handoff_metadata.
-
v2.1.290
Cloud sessions now say which local hooks they will not receive
When work moves to a cloud session, Claude Code withholds hooks from files the cloud session could change and tells you which ones
gate cited by this entry
-
v2.1.285
Remote session bridge reports read receipts and delivery
The connection to remote sessions can now report when incoming messages are read and delivered, and flush streamed output sooner
gate cited by this entry
-
v2.1.248
Worktree state reporting to the remote bridge stays off
Reporting worktree dirtiness and unpushed commits to the remote bridge stays off.
gate cited by this entry, found in this entry's text
-
v2.1.242
Cloud sessions can report git worktree state on handoff
Handing a session to the cloud can include a snapshot of your checkout, off by default.
gate cited by this entry, found in this entry's text
Gate readings
4| 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 |
| v2.1.285 read on another version | Off by default, switched on for this account | on | on | off |
| v2.1.248 | Off by default, switched on for this account | on | on | off |
| v2.1.242 | Off in both readings | off | off | 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
12| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| anonymous | on | 2026-10-17T05:30:04Z | 2026-10-22T06:25:04Z | v2.1.302 to v2.1.308 |
| this account | on | 2026-09-10T21:47:12Z | 2026-10-22T06:25:04Z | v2.1.268 to v2.1.308 |
| anonymous | no longer carried | 2026-10-17T05:25:57Z | 2026-10-17T05:25:57Z | v2.1.302 |
| anonymous | on | 2026-08-26T17:10:04Z | 2026-10-17T05:10:04Z | v2.1.246 to v2.1.302 |
| this account | no longer carried | 2026-09-10T21:46:45Z | 2026-09-10T21:46:45Z | v2.1.268 |
| this account | on | 2026-09-08T20:36:15Z | 2026-09-10T17:40:05Z | v2.1.263 to v2.1.267 |
| this account | no longer carried | 2026-09-08T20:34:58Z | 2026-09-08T20:34:58Z | v2.1.265 |
| this account | on | 2026-09-06T02:40:05Z | 2026-09-08T18:45:05Z | v2.1.261 to v2.1.263 |
| this account | no longer carried | 2026-09-06T02:36:19Z | 2026-09-06T02:36:19Z | v2.1.263 |
| this account | on | 2026-08-26T18:15:04Z | 2026-09-06T01:55:04Z | v2.1.246 to v2.1.261 |
| this account | off | 2026-08-19T13:30:05Z | 2026-08-26T18:10:04Z | v2.1.233 to v2.1.246 |
| anonymous | off | 2026-08-19T13:20:04Z | 2026-08-26T16:05:04Z | v2.1.233 to v2.1.246 |
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_handoff_metadata was v2.1.242, 24 Aug 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
56One 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.