Archive sync now tells you plainly about conflicts, restored deletes and files too large to sync.
What's wrong with this entry?
The archive engine narrates what it did rather than acting silently. Conflicted files are described with where each copy landed, deletes the agent made that you still have locally are reported as restored, oversize files are named as "too large to sync and will not arrive", and deferred deletes and uploads are announced as arriving with your next messages. A fresh container is described as having "came back without this folder's files".
- Each stop condition gets its own line and emits
tengu_dir_sync_stopped: withdrawn, switched off, lane unavailable, listing abandoned. - Pulls and pushes emit
tengu_dir_sync_pullandtengu_dir_sync_pushwith an outcome and counts of applied, conflicted and trashed files. - Setting
CLAUDE_CODE_DIR_SYNC_DISABLE_ANCHORINGprints a warning that files are read by name and the protection against a cloud session redirecting a read through a swapped directory is off.
File sync is reading this folder's files by name (CLAUDE_CODE_DIR_SYNC_DISABLE_ANCHORING is set): the protection against a cloud session redirecting a read through a swapped directory is off
Strings lifted out of the shipped bundle, so the claim above can be checked against them.