{"version":"2.1.224","anchor":"directory-sync-apply-starts-with-the-working-file-syncer","canonical_anchor":"directory-sync-apply-starts-with-the-working-file-syncer","heading":"Directory sync apply starts with the working-file syncer","tier":"internal","area":"Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/directory-sync-apply-starts-with-the-working-file-syncer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Directory sync apply starts with the working-file syncer\n\nStartup also starts a directory sync apply step alongside the working-file syncer in normal local sessions.\n\n**What**\n\nStartup now also loads and starts directory sync apply for the current directory, in the same branch that starts the working-file syncer, and logs `dir_sync_apply_import_failed` if that load fails. The branch runs only when both `CLAUDE_CODE_ENVIRONMENT_KIND` and `CLAUDE_CODE_DISABLE_WORKING_SYNC` are unset, which is the normal local case.\n\n**Evidence**\n\n`dir_sync_apply_import_failed`\n\n- Area: Sync\n- Names: `CLAUDE_CODE_ENVIRONMENT_KIND`, `CLAUDE_CODE_DISABLE_WORKING_SYNC`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}