You'll notice
Useful2 Signal2
Background file sync now skips itself while a sync-sensitive command is running.
What's wrong with this entry?
Anonymous. No account, no email.
What
The background pass that syncs your working directory to a cloud session now runs as a distinct "watch" pass. When a command that is sensitive to syncing is already running, the watch pass is skipped rather than run, and it tells you sync keeps trying at each sync point instead of using the message-blocking wording reserved for foreground sends.
Details
- The skip is recorded with the reason
held_for_command. - Foreground triggers (sending a message, creating or capturing a session) are unaffected and still run their pass immediately.
- The trigger type is set internally by whichever code path starts the pass; there is no setting for it.
Evidence
held_for_command
Strings lifted out of the shipped bundle, so the claim above can be checked against them.