What
File sync across machines now explains, in plain language, each reason a command was held or deferred and what clears it: the branch changed, capped until upload finishes, an upload-only device, files still arriving, the peer is serving another command, sync stopped there, or the other side's engine is too old to sync mid-turn. Read-only tool calls are never held; they run and carry a note instead.
Details
- Each message pairs a cause with a remedy rather than just refusing.
- The oldest-engine case tells you the command ran against that machine's files as of the user's last message, so your recent edits may be missing.
Evidence
syncs this session's files only at turn boundaries (its sync engine has no mid-turn sync points); the command ran on that machine's files as of the user's last message, which may not include your edits here
Strings lifted out of the shipped bundle, so the claim above can be checked against them.