{"version":"2.1.248","anchor":"github-access-via-a-synced-token-no-longer-needs-a-remote-fl","canonical_anchor":"github-access-via-a-synced-token-no-longer-needs-a-remote-fl","heading":"GitHub access via a synced token no longer needs a remote flag","tier":"notice","area":"GitHub Integration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/github-access-via-a-synced-token-no-longer-needs-a-remote-fl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### GitHub access via a synced token no longer needs a remote flag\n\nRepo access through your gh CLI token no longer sits behind an off-by-default remote flag.\n\n**What**\n\nReporting repo access through the token synced from your `gh` CLI login used to sit behind a remote flag that defaulted to off. That check is gone, so the token-sync access method is now reachable for anyone the remaining local check allows.\n\n**Details**\n\n- The branch still runs after the app-install check and still requires the token-sync probe to succeed.\n\n**Evidence**\n\n`method: \"token-sync\"`\n\n- Area: GitHub Integration\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}