GitHub: during unusual traffic, some anonymous HTTPS clones of public repositories may temporarily require authentication
Anonymously pulling public repositories is no longer guaranteed; CI and sandboxed agents are the most likely to hit it.
// Key points
- During unusual traffic GitHub may temporarily require authentication for some HTTPS clones and fetches of public repositories, failing with an authentication-required message; it's temporary, not a general requirement for public repos.
- Authenticated HTTPS operations, SSH, pushes, and other web and API traffic are unaffected.
- For automation GitHub recommends authenticating: the built-in GITHUB_TOKEN in Actions, and a GitHub App installation token (or a personal access token) in other CI.
Builder's takeCoding agents that git clone dependency repos the moment a sandbox starts are exactly the traffic this will hit. I'd give every automated clone one read-only GitHub App token, and add a backoff retry in the agent's tool layer so a temporary block doesn't fail the whole run.
// Background · from #Coding agents
Full timeline →- Oct 20 Cloudflare cuts the average cost of its internal AI code review 68%, from $2.43 to $0.77
- Oct 20 GitHub opens a Copilot model policy REST API at enterprise, team, app and organization level, generally available
- Oct 20 Copilot retires six models including GPT-5.5 and GPT-5.4 on October 19, pointing users to GPT-6.1 Sol and GPT-6 Luna