{"version":"2.1.310","anchor":"github-proxy-tls-failure-message","canonical_anchor":"github-proxy-tls-failure-message","heading":"Managed GitHub access through a session proxy: standalone proxy support and a failure message","tier":"notice","area":"Git","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/github-proxy-tls-failure-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Managed GitHub access through a session proxy: standalone proxy support and a failure message\n\nManaged git and gh access can now go through a standalone proxy URL, and a new message tells Claude not to bypass TLS checks when setup fails\n\n**What**\n\nIn some sessions, Anthropic sets up access to GitHub through a proxy, a go-between server. Both `git` and `gh`, the GitHub command-line tool, are routed through it.\n\n- The code that writes the git settings and the `gh` wrapper can now use a standalone proxy at its own `proxyUrl`. Before, it always used a local relay at `http:\/\/127.0.0.1` and a port number.\n\n- The safety checks now also reject a proxy URL that contains a quote or a newline. They already did this for the certificate bundle path.\n\n- A new message covers the case where this access could not be set up because `git` and `gh` fail TLS verification against github.com. TLS verification is the check that a secure connection is genuine. The message tells Claude not to turn off TLS verification and not to edit the `GIT_CONFIG_GLOBAL` file. Instead, Claude should tell you GitHub is unavailable.\n\n**Why**\n\nManaged GitHub access can work without a local relay. If it breaks, Claude reports the problem instead of weakening connection security to work around it.\n\n- Area: Git\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}