{"version":"2.1.310","anchor":"governed-git-with-a-self-hosted-agent-proxy-is-now-allowed-i","canonical_anchor":"governed-git-with-a-self-hosted-agent-proxy-is-now-allowed-i","heading":"Self-hosted agent proxy can now carry Anthropic-managed git sessions in some cases","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/governed-git-with-a-self-hosted-agent-proxy-is-now-allowed-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Self-hosted agent proxy can now carry Anthropic-managed git sessions in some cases\n\nAnthropic-managed git sessions can now run through a self-hosted agent proxy, except on Windows and in a few other cases\n\n**Unclear.** It is not clear whether the server ever asks for the new kind of governed git that this mode now accepts.\n\n**What**\n\nA self-hosted runner can send a session's traffic through your own agent proxy, a go-between server you run. Before, any session that used Anthropic-managed git (governed git) was refused in this mode. Now the runner looks at which kind of governed git the session asks for:\n\n- Off: proceeds as before\n\n- Legacy: still refused\n\n- On: proceeds, unless one of the cases below applies\n\nA session asking for the new kind is still refused when:\n\n- It runs on Windows\n\n- The server sends no git setup for it\n\n- The runner cannot check the Claude Code version, because it is started with a pinned `--exec-path` or a command hook\n\nThe runner's warning text was reworded to match these rules.\n\n**Why**\n\nIf you run a self-hosted runner with your own proxy, Anthropic-managed git sessions no longer have to be refused outright.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}