{"version":"2.1.248","anchor":"directory-sync-loads-a-mid-turn-hook-from-a-separate-build-c","canonical_anchor":"directory-sync-loads-a-mid-turn-hook-from-a-separate-build-c","heading":"Directory sync loads a mid-turn hook from a separate build chunk","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/directory-sync-loads-a-mid-turn-hook-from-a-separate-build-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Directory sync loads a mid-turn hook from a separate build chunk\n\nDirectory sync loads an extra chunk to register a mid-turn hook, logging failures.\n\n**What**\n\nWhen the managed cloud worker starts syncing your directory, it now also loads a separate build chunk and registers a mid-turn hook. If that load fails it logs `dir_sync_mid_turn_import_failed` at warn level and continues.\n\n**Details**\n\n- The hook's implementation is in a build chunk that is not part of the readable bundle, so what it does mid-turn is not visible here; only that dir sync now has a mid-turn registration path alongside its existing start path.\n- Reachable only when the dir-sync worker runs; setting `CLAUDE_CODE_DISABLE_DIR_SYNC` suppresses it.\n\n**Evidence**\n\n`dir_sync_mid_turn_import_failed`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}