Unclear What a cloud session now does when its repository access is throttled is not stated.
What
When 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.
The 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.
Why
Cloud sessions may now behave differently when GitHub limits how often they can access a repository.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What a cloud session now does when its repository access is throttled is not stated.