tengu_ccr_bundle_seed_enabled
A Claude Code feature flag, read out of the shipped bundle. It was in the build from v2.1.227 and was gone by v2.1.242.
If a folder is too big to seed a cloud session, you now see the size, cap and biggest files.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.246.
In the changelogs
6Releases whose published page names tengu_ccr_bundle_seed_enabled.
-
v2.1.273
Cloud/bridge session bundle-seeding gated by tengu_ccr_bundle_seed_enabled
Seeding a remote or bridged session from a local git bundle stays behind the tengu_ccr_bundle_seed_enabled gate
gate cited by this entry, found in this entry's text
-
v2.1.273
Bundle-seeding for remote teleport sessions, gated by an unresolved flag
Remote teleport sessions can now seed the workspace with a git bundle, controlled by env vars and a flag
gate cited by this entry, found in this entry's text
-
v2.1.248
Folder seeding stops short of uploading
Preparing a folder for a cloud session now packages it and hands it off without uploading.
gate cited by this entry, found in this entry's text
-
v2.1.247
Cloud session uploads stage a private, sanitized copy of your git metadata
Uploading a repo to a cloud session can read a scrubbed private copy of your git metadata.
named in this entry, gate cited by this entry, found in this entry's text
-
v2.1.246
Folder-seed refusals name the size, the cap and the largest files
If a folder is too big to seed a cloud session, you now see the size, cap and biggest files.
gate cited by this entry, found in this entry's text
-
v2.1.246
Cloud sessions can start from a plain folder, not just a git checkout
Cloud sessions can start from a plain folder, but only if you switch the bundle seeding on.
gate cited by this entry, found in this entry's text
Gate readings
5| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.273 read on another version | Gate removed from the code | on | on | not a boolean we can read |
| v2.1.248 | Gate removed from the code | on | on | not a boolean we can read |
| v2.1.247 | Gate removed from the code | on | on | not a boolean we can read |
| v2.1.246 | Gate removed from the code | on | on | not a boolean we can read |
| v2.1.238 | Gate removed from the code | on | on | not a boolean we can read |
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-22T08:25:04Z | v2.1.302 to v2.1.308 |
| this account | on | 2026-09-10T21:47:12Z | 2026-10-22T08: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-19T04:25:04Z | 2026-10-17T05:10:04Z | v2.1.233 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-14T22:10:05Z | 2026-09-06T01:55:04Z | v2.1.232 to v2.1.261 |
| anonymous | no longer carried | 2026-08-19T04:20:14Z | 2026-08-19T04:20:14Z | v2.1.233 |
| anonymous | on | 2026-08-14T22:10:05Z | 2026-08-19T03:45:04Z | v2.1.232 to v2.1.233 |
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
3The earliest release whose published evidence quoted tengu_ccr_bundle_seed_enabled was v2.1.246, 25 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
2Build by build
70One 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.