Follow Discord
Sweep 23 Oct 2026 · 21:48Z Build v2.1.310 529 read Stable v2.1.308 Latest v2.1.309 Next v2.1.310 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.310entry #30

Claude Code v2.1.310 ·

Self-hosted agent proxy can now carry Anthropic-managed git sessions in some cases

Anthropic-managed git sessions can now run through a self-hosted agent proxy, except on Windows and in a few other cases

You'll notice Improvements
JSON All of v2.1.310
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Self-Hosted RunnersArea: what it touches
ImprovementsKind: in v2.1.310,
ImprovementsSection of the release

Unclear It is not clear whether the server ever asks for the new kind of governed git that this mode now accepts.

What

A 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:

  • Off: proceeds as before
  • Legacy: still refused
  • On: proceeds, unless one of the cases below applies

A session asking for the new kind is still refused when:

  • It runs on Windows
  • The server sends no git setup for it
  • The runner cannot check the Claude Code version, because it is started with a pinned --exec-path or a command hook

The runner's warning text was reworded to match these rules.

Why

If you run a self-hosted runner with your own proxy, Anthropic-managed git sessions no longer have to be refused outright.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether the server ever asks for the new kind of governed git that this mode now accepts.

See this entry in the whole of v2.1.310 →

Feedback