Cloud session file sync could pull changes back to your directory and narrate it, but the gate is off.
Two-way per-turn sync runs only under tengu_violin_wood, which falls back to off, for container_sync directories.
tengu_violin_wood Off in both readingsThe 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.228: on
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.228. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The per-turn file sync with a cloud session now pulls as well as pushes, and narrates what it did in plain language, with lines beginning "Pulled " or "Synced " and warnings such as "the session's file budget is used up" or "names that differ only by case". It runs only when the flag tengu_violin_wood is on, which falls back to off, and only for directories whose sync mode is container_sync.
- Incoming changes that conflict with local edits are written to an
.incoming-staging file so both copies survive. - Two new telemetry events,
tengu_dir_sync_pushandtengu_dir_sync_pull, carry per-turn counts of applied rows, conflicts, stale entries, deferred rows, bytes written and case collisions. - Pull is skipped on Windows and reports
unsupported_platform. The user is told: "On Windows, files Claude changes in the cloud session are not synced back to this directory yet; your changes here still sync to it".
the session's file budget is used up
Strings lifted out of the shipped bundle, so the claim above can be checked against them.