{"version":"2.1.282","anchor":"directory-sync-file-sync-timing-guidance-lost-one-variant","canonical_anchor":"directory-sync-file-sync-timing-guidance-lost-one-variant","heading":"Directory sync timing note to Claude now always uses one wording","tier":"internal","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/directory-sync-file-sync-timing-guidance-lost-one-variant","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Directory sync timing note to Claude now always uses one wording\n\nClaude's note about when command output from an attached machine shows up locally now always uses the \"not necessarily by your next step\" wording\n\n**Unclear.** It is not clear which sessions used to receive the \"never within one script\" wording.\n\n**What**\n\nIn sessions where files are kept in step with an attached machine (directory sync), Claude Code gives Claude a note about when output from commands run on that machine appears locally. That note used to choose between two phrasings. It now always says the output arrives \"not necessarily by your next step\". The stricter \"never within one script\" phrasing is no longer used.\n\n**Why**\n\nThis changes only what Claude is told, not how the sync itself works. Sessions that used to get the stricter wording are now told the same thing as every other directory-sync session.\n\n- Area: File Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}