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.224 Home All releases ←olderv2.1.223 v2.1.225newer→
Claude Code v2.1.224

Untracked files can be uploaded to a cloud session's working directory

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

Cloud sessions can upload untracked files, but only behind an off-by-default gate and a project setting.

Untracked-file seeding with 192-file and 100 MB ceilings is built but requires the tengu_violin_wood gate, which falls back to off, plus remoteFileMode set to container_sync.

Feature flag
tengu_violin_wood Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

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

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

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

remoteFileModecontainer_sync
What

Cloud sessions can now start from more than the git bundle. A new seeding step finds files that are untracked but not gitignored, hashes them and uploads them to the session, with hard ceilings of 192 files, 104857600 bytes (100 MB) and a 60 second deadline. It is off unless the tengu_violin_wood gate is on (it falls back to off, including on any error) and the project setting remoteFileMode is container_sync. Otherwise the session starts from the git bundle alone.

Details
  • The file list comes from git ls-files --others --exclude-standard -z at the git root, and dependency directories are filtered out: node_modules, venv, .venv, __pycache__, build, dist, target, vendor.
  • Symlinks, hard links, oversize files and files outside the git root are skipped.
  • Each file is uploaded to the session's synced_file endpoint along with a manifest listing what was sent.
  • You see a per-file progress line and a summary. When the feature is unavailable you get "Cloud file sync is unavailable for this session; starting from the git bundle alone".
  • Telemetry: tengu_dir_sync_inventory carries per-reason skip counts including skipped_too_large, skipped_symlink and skipped_over_budget; upload start/complete and tengu_dir_sync_seed_complete record the outcome.
Evidence

tengu_dir_sync_inventory, tengu_dir_sync_seed_complete

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

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.224 →