{"version":"2.1.281","anchor":"directory-sync-tells-the-agent-when-the-users-blocked-chang","canonical_anchor":"directory-sync-tells-the-agent-when-the-users-blocked-chang","heading":"Directory sync tells the agent when the user's blocked changes start arriving again","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/directory-sync-tells-the-agent-when-the-users-blocked-chang","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Directory sync tells the agent when the user's blocked changes start arriving again\n\nIn cloud sessions, Claude is now told when your blocked changes start reaching its checkout again, and to re-read files\n\n**What**\n\nIn a cloud session, directory sync copies your changes into the checkout Claude works in. Sometimes it cannot apply them, for example when branch names collide or the checkout is partway through a merge, and Claude gets a \"not taken\" notice. Claude is now also told when your updates start being applied again, and is asked to re-read files.\n\nTwo related changes:\n\n- `released`: this not-taken reason no longer sends Claude a notice.\n\n- Not-taken lines in your report are now shown once instead of being added again every turn.\n\n**Why**\n\nClaude now knows when the files it sees have caught up with yours, so it is less likely to keep working from out-of-date copies. Your report also no longer fills up with the same line turn after turn.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}