Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code 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.

Nothing to try yet Notable No documentation found In Development
JSON All of v2.1.247
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
In DevelopmentKind: in v2.1.247,
What probably matters to youSection of the release

The sanitized git staging directory only runs on the bundle route, via CCR_FORCE_BUNDLE, CCR_ENABLE_BUNDLE or a server gate with no local fallback.

What

A new module builds a throwaway git directory under ~/.claude/seed-admin when a cloud session uploads your repo as a bundle, so the upload reads a scrubbed copy of HEAD, refs and the index rather than your working .git. It only runs when the bundle route is taken: set CCR_FORCE_BUNDLE or CCR_ENABLE_BUNDLE, or have the remote gate tengu_ccr_bundle_seed_enabled on. That gate has no compiled fallback at the call site, so off the env vars it is entirely the server's call.

Details
  • The staged directory gets a fresh config carrying only a whitelist of safe keys such as core.autocrlf, core.eol, core.symlinks and core.filemode, with automatic gc and maintenance disabled. The index, packed-refs and shallow files are copied and the object store is linked in (via a junction on Windows).
  • It refuses with plain reasons, including that HEAD is not a branch or an object id, that too many shared-index files are present, and placement checks that the staged directory is not inside your checkout or is not a plain directory owned by you.
  • The git environment is scrubbed of GIT_EXEC_PATH, LD_PRELOAD, DYLD_INSERT_LIBRARIES and similar before anything runs, and leftover directories from earlier crashed runs are swept.
  • The upload path gained failure text explaining that this directory is made under ~/.claude/seed-admin from the checkout's HEAD and index.
Evidence

~/.claude/seed-admin is not a plain directory of this user

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_ccr_bundle_seed_enabled Gate removed from the code

This release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.

This account: on · anonymous baseline: on · compiled default in v2.1.247: not a boolean we can read

Read once, for one account on one subscription tier, against v2.1.247. It isn't a statement about your account. What a flag value here can and cannot tell you

Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Environment variables touched a line naming CCR_FORCE_BUNDLE after this was published. | `CCR_FORCE_BUNDLE` | Set to `1` to force [`claude --cloud`](/docs/en/claude-code-on-the-web#send-local-repositories-without-github) to bundle and upload your local repository instead of cloning from its remote | env-vars see the edit
Confirmed since Anthropic's documentation has since written up CCR_FORCE_BUNDLE, on Use Claude Code on the web. To upload a bundle even when Claude Code would otherwise clone from the remote, set `CCR_FORCE_BUNDLE=1`: claude-code-on-the-web see the edit
What has happened since
Gate removed from the code v2.1.273 removed the tengu_ccr_bundle_seed_enabled gate from the code while it was still reading on for the account this site reads. The code path no longer asks a flag before it runs.
Flag reading moved The flag server now returns on for tengu_ccr_bundle_seed_enabled, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_ccr_bundle_seed_enabled, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Gate removed from the code v2.1.248 removed the tengu_ccr_bundle_seed_enabled gate from the code while it was still reading on for the account this site reads. The code path no longer asks a flag before it runs.
Gate removed from the code v2.1.247 removed the tengu_ccr_bundle_seed_enabled gate from the code while it was still reading on for the account this site reads. The code path no longer asks a flag before it runs.
Gate removed from the code v2.1.246 removed the tengu_ccr_bundle_seed_enabled gate from the code while it was still reading on for the account this site reads. The code path no longer asks a flag before it runs.
Gate removed from the code v2.1.238 removed the tengu_ccr_bundle_seed_enabled gate from the code while it was still reading on for the account this site reads. The code path no longer asks a flag before it runs.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up CCR_FORCE_BUNDLE, on Use Claude Code on the web.

See this entry in the whole of v2.1.247 →

Feedback