{"version":"2.1.277","anchor":"new-separate-checkout-project-location-kind","canonical_anchor":"new-project-sync-status-users-disconnected-separate-copy","heading":"New 'separate copy' concept for a session's project location and sync status","tier":"notice","area":"Remote Machines","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/new-separate-checkout-project-location-kind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### New 'separate copy' concept for a session's project location and sync status\n\nClaude Code now distinguishes a session's own dedicated 'separate copy' checkout from other project sync states, in UI text and telemetry\n\n**What**\n\n- Tool-context location descriptions gained a \"separate\" case describing a location as the session's own dedicated checkout \u2014 \"the primary copy for this session's work\" \u2014 alongside the existing default\/machine\/unknown cases.\n\n- The device\/session sync telemetry payload gained an optional `folder_relation` field that accepts the value `separate_copy`, alongside the existing `project_sync` enum.\n\n- The status text describing a session's synced project directory gained a new case for when the project is the user's own separate copy with sync turned off, showing distinct wording instead of falling back to a generic \"not synced\" message.\n\n**Why**\n\nThis gives Claude Code a consistent way to describe and record when a session is working from its own separate checkout rather than a directly synced copy, making status messages and sync telemetry clearer.\n\n- Area: Remote Machines\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}