{"version":"2.1.283","anchor":"remote-sessions-carry-a-monorepo-option-and-surface-a-no","canonical_anchor":"remote-sessions-carry-a-monorepo-option-and-surface-a-no","heading":"--remote now tells you when the directory sync offer was put off","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/remote-sessions-carry-a-monorepo-option-and-surface-a-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### `--remote` now tells you when the directory sync offer was put off\n\nIf a `--remote` session's directory sync offer is deferred because its anchor is unavailable, you now see a warning instead of nothing\n\n**Unclear.** It is not clear where the monorepo setting comes from or what sets it.\n\n**What**\n\nWhen `claude --remote` starts a cloud session, Claude Code can offer to sync your local directory to it. Sometimes that offer is put off because the anchor it needs is unavailable. In that case, its explanation is now added to the warning notices shown for the session. Before, only the notices from creating the session itself were shown, and this one was dropped without a word.\n\nThe sync offer and the session creation also both receive a monorepo setting now. A monorepo is a single repository that holds several projects.\n\n**Why**\n\nYou are now told why directory sync was not offered, instead of seeing nothing.\n\n- Area: Cloud Sync\n- Names: `--remote`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}