Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.246 Home All releases ←olderv2.1.245 v2.1.247newer→
Claude Code v2.1.246

Cloud sessions can start from a plain folder, not just a git checkout

Not switched on
Useful3 Signal5
Cloud Sessions Notable not in their notes

Cloud sessions can start from a plain folder, but only if you switch the bundle seeding on.

In-process git bundle seeding from a non-git folder is built but refuses unless CCR_ENABLE_BUNDLE is set or tengu_ccr_bundle_seed_enabled is on.

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.246: not a boolean we can read

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

CCR_ENABLE_BUNDLE
What

A directory that is not a git repository can now seed a cloud session. Claude Code packages the folder into a git bundle in-process, no git binary required, and uploads it as _source_seed.bundle. The seeding step is skipped unless you set the environment variable CCR_ENABLE_BUNDLE or the remote switch tengu_ccr_bundle_seed_enabled is on, in which case starting from a folder refuses with a message saying the feature is switched off.

Details
  • The seed builds a single parentless commit ("sync 0"), packs it, and uploads it; the session's local record stores a new start kind carrying the folder pin and the seeded tree.
  • Size and file-count caps apply, and files that change while being read trigger a "busy" refusal. Failures surface as folder_too_large or folder_seed_failed.
  • The teleport path that creates a session imports the folder seeder on demand and reports progress; when the switch is off it records reason bundle_seed_switched_off.
  • Telemetry: success logs tengu_dir_sync_folder_session with the engine, seeded file count and byte count; refusals log dir_sync_folder_refused and folder_seed_refused; uploads report through tengu_ccr_bundle_upload with scope "folder".
  • Entering the folder branch at all also depends on a separate folder opt-in check whose negative answer is folder_not_opted_in; what sets that opt-in is not visible in the folder-seed code itself.
Evidence

Cannot start a cloud session from this folder right now: starting sessions from local files is switched off. Try again later., folder_seed_refused, tengu_ccr_bundle_seed_enabled

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

Usage
CCR_ENABLE_BUNDLE=1 claude

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.246 →