You'll notice
Useful3 Signal2
Messages to a cloud session wait until your uploaded files have actually landed there.
What's wrong with this entry?
Anonymous. No account, no email.
What
When directory sync is on, a message you send to a cloud session is held until the session confirms it applied the files uploaded from your machine, polled with exponential backoff up to a cap. If that never happens you get a plain-language explanation instead of silence.
Details
- Timeout produces its own message; a partial apply names how many files could not be fetched.
- Each container-side refusal maps to a sentence, covering a bundle timeout, the uploaded state not being a descendant of what the session has, a dirty working tree, a refused checkout and a git timeout.
- Two new telemetry events record the wait and each held send.
- Only sessions with directory sync active reach this path.
Evidence
tengu_dir_sync_seed_gate_send
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.
-
v2.1.238
Sync state machine gains a moved-root case and a per-turn pull hook
Both mention directory
-
v2.1.238
Untracked-file survey extracted and shared
Both mention directory
-
v2.1.238
Sync internals reshaped around per-file credential state
Both mention directory