Startup also starts a directory sync apply step alongside the working-file syncer in normal local sessions.
What's wrong with this entry?
Startup 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.
dir_sync_apply_import_failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.227
Remote worker sessions now sync the working directory both ways around every turn
Both mention environment kind disable working
-
v2.1.221
Headless MCP startup wait reworked
Both mention environment kind
-
v2.1.248
MCP errors sent to Remote Control clients are filtered to a fixed list
Both mention environment kind