{"version":"2.1.288","anchor":"github-proxy-errors-split-into-refused-vs-temporary","canonical_anchor":"github-proxy-errors-split-into-refused-vs-temporary","heading":"GitHub proxy errors now say whether to retry","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/github-proxy-errors-split-into-refused-vs-temporary","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### GitHub proxy errors now say whether to retry\n\nWhen the GitHub proxy fails, Claude Code now tells a refused connection apart from one that could not open, and suggests one retry for the second\n\n**What**\n\nSome sessions reach GitHub through a proxy, a middleman service that carries the connection, and Claude Code provides a stand-in for the `gh` command (GitHub's command-line tool) that goes through it. When that proxy fails, the error message now names one of two cases:\n\n- The proxy refused the connection. As before, the advice is not to retry the same request unchanged.\n\n- The proxy could not open the connection. The message now says to wait and retry once, then check the proxy's status endpoint, an address that reports whether the proxy is working.\n\nBefore this change, every failure was reported as a refused connection with advice not to retry.\n\n**Why**\n\nA connection that could not open is often a passing problem. With the new message, Claude can retry these short-lived failures instead of giving up as if the request had been refused.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}