{"version":"2.1.283","anchor":"cloud-session-the-monorepo-flag-source-is-no-longer-treated","canonical_anchor":"cloud-session-the-monorepo-flag-source-is-no-longer-treated","heading":"Remote sessions started by the monorepo flag are no longer handled as project sessions","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/cloud-session-the-monorepo-flag-source-is-no-longer-treated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Remote sessions started by the monorepo flag are no longer handled as project sessions\n\nWhen a new remote session was started because of the monorepo flag, Claude Code no longer records its settings scope as \"project\"\n\n**Unclear.** What the \"project\" scope controls later in the session is not stated.\n\n**What**\n\nWhen Claude Code starts a new remote session (one that runs in the cloud rather than on your machine), it records which settings scope the session uses, and some start-up reasons are excluded from being recorded as \"project\". The reason `monorepo_flag` is now excluded too, alongside `github_preflight_failed` and `monorepo_env_no_checkout`.\n\n**Why**\n\nRemote sessions started for this reason no longer get project-scoped handling.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}