{"version":"2.1.311","anchor":"git-checkout-validateaccess-accepts-skippedifthrottled","canonical_anchor":"git-checkout-validateaccess-accepts-skippedifthrottled","heading":"Repository access check in cloud session setup can account for throttling","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/git-checkout-validateaccess-accepts-skippedifthrottled","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Repository access check in cloud session setup can account for throttling\n\nWhen a cloud session sets up its git repository, the access check now learns whether it was skipped because of throttling\n\n**Unclear.** What a cloud session now does when its repository access is throttled is not stated.\n\n**What**\n\nWhen a cloud session sets up its git repository, Claude Code checks that it has access to that repository. That check used to receive only the repository. It now also receives whether the check was skipped because access was being throttled, meaning limited for making too many requests.\n\nThe step that checks out a specific branch or commit no longer receives the extra inputs it used to, including the one for a standby checkout.\n\n**Why**\n\nCloud sessions may now behave differently when GitHub limits how often they can access a repository.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}