{"version":"2.1.238","anchor":"directory-sync-stops-asking-which-sync-mode-to-use-in-the-an","canonical_anchor":"directory-sync-stops-asking-which-sync-mode-to-use-in-the-an","heading":"Directory sync stops asking which sync mode to use in the Anthropic monorepo","tier":"notice","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/directory-sync-stops-asking-which-sync-mode-to-use-in-the-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Directory sync stops asking which sync mode to use in the Anthropic monorepo\n\nSync no longer asks which mode to use when the repo might be the Anthropic monorepo.\n\n**What**\n\nClaude Code reads the repository's git config and remotes to decide whether a directory could be the Anthropic monorepo. If it cannot rule that out, or the config cannot be read at all, the sync-mode prompt is skipped and recorded with the reason `monorepo_or_unreadable_config`. The same check drives which memory guideline paths cowork uses. This runs unconditionally, with no flag.\n\n**Evidence**\n\n`monorepo_or_unreadable_config`\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}