{"version":"2.1.281","anchor":"dir-sync-after-a-forwarded-command-the-session-no-longer-p","canonical_anchor":"dir-sync-after-a-forwarded-command-the-session-no-longer-p","heading":"Dir-sync: after a forwarded command, the session no longer pulls the machine's changes mid-turn","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/dir-sync-after-a-forwarded-command-the-session-no-longer-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Dir-sync: after a forwarded command, the session no longer pulls the machine's changes mid-turn\n\nAfter a forwarded command, directory sync no longer pulls the remote machine's changed files in the middle of a turn\n\n**Unclear.** The finding does not say whether or when the remote changes are pulled instead.\n\n**What**\n\nDirectory sync keeps files matching between your machine and a remote one. When a command is forwarded to the remote machine, Claude Code no longer waits after it to pull the remote machine's changed files and apply them while the turn (one round of Claude working on your request) is still going. It now only adds a short note.\n\nThe notes changed:\n\n- a new note says 'uploads are not getting through to the sync service just now' when uploads fail\n\n- the 'not_attempted', 'unchanged' and 'sent' cases now add no note at all\n\nThis area involves the `tengu_dir_sync_mid_turn` gate, a server-controlled switch.\n\n**Why**\n\nFiles changed on the remote machine by a forwarded command do not appear locally part way through a turn, and you are told when uploads are failing."}