{"version":"2.1.300","anchor":"remote-session-attach-path-self-hosted-runner-check","canonical_anchor":"remote-session-attach-path-self-hosted-runner-check","heading":"Remote sessions on self-hosted runners skip the project sync check","tier":"notice","area":"Self-Hosted Runner","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/remote-session-attach-path-self-hosted-runner-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Remote sessions on self-hosted runners skip the project sync check\n\nWhen attaching to a remote session on a self-hosted runner, Claude Code now skips checking whether the project is synced\n\n**What**\n\nWhen Claude Code attaches to a remote session running on a self-hosted runner, a machine your organization runs itself, it now follows a separate plan and no longer checks whether the project is synced. Before, it always checked.\n\n**Why**\n\nThis changes how sessions behave on self-hosted runners.\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}