Self-hosted runners gain a git-proxy opt-in and git-routing flags

Self-hosted runner CLI adds --use-anthropic-git-proxy plus git remote rewriting and drain-wait flags

Group of 2 Use it now New Features

JSON All of v2.1.267

Use it nowTier: how much it should matter to you

4Useful: my rating, 1 to 5

3Signal: worth watching, 1 to 5

Self-Hosted RunnerArea: what it touches

New FeaturesKind: in v2.1.267, 09 Sep 26

What probably matters to youSection of the release

What

A new --use-anthropic-git-proxy flag lets a self-hosted runner opt into having Anthropic manage git authentication server-side (using the session creator's GitHub OAuth token, or the org's GitHub App token for bot/agent sessions) instead of configuring git auth on the runner itself. Registration logs "Registering as opted in to Anthropic-managed git (--use-anthropic-git-proxy)"; if the server can't provide governed git for a session despite the flag, a warning explains the fallback to the legacy clone-URL proxy (deprecated).
New --git-ssh-rewrite <host> and --git-host-rewrite <f>=<t> flags let a runner rewrite git remote URLs, useful for SSH-only hosts or split-horizon DNS setups.
The SELF_HOSTED_RUNNER_DRAIN_WAIT_MS environment variable (default 0, meaning SIGTERM is sent immediately; max 86400) controls how long a runner waits before shutting down, with --drain-wait-bg-tasks-sec documented as a deprecated alias.

Why

This gives self-hosted runner operators more control over how git authentication and remote URLs are handled, and how long a runner waits for background tasks before terminating.

What the documentation says

--use-anthropic-git-proxy Claude Code changelog modified, high confidence * Self-hosted runner: Changed `--use-anthropic-git-proxy` to be reported to the server at registration and to print a warning for each session that still clones through the legacy git proxy see the edit

--use-anthropic-git-proxy Deploy self-hosted environments to production modified, medium confidence The runner also reports the opt-in to Anthropic when it registers, printing `Registering as opted in to Anthropic-managed git (--use-anthropic-git-proxy)` at startup. Each session on an opted-in runner then uses either Anthropic-managed gi… see the edit

--use-anthropic-git-proxy Self-hosted environments reference modified, medium confidence | `--use-anthropic-git-proxy` | `CLAUDE_RUNNER_USE_GIT_PROXY=1` | off | Clone via the [Anthropic git proxy](/docs/en/self-hosted-environments-deploy#use-the-anthropic-git-proxy) instead of customer-managed git auth. Requires `--capacity 1`… see the edit

How sure we are

Two sources agreeTwo things we can check say the same as this entry.

Anthropic's documentation agrees--use-anthropic-git-proxy on Claude Code changelog

Anthropic's release notes agreeSelf-hosted runner: Changed --use-anthropic-git-proxy to be reported to the server at registration and to print a warning for each session…

See this entry in the whole of v2.1.267 →

The build it came inv2.1.267

9 Sep 2026 · 270 entries, this one is #10.

Use it now38
You'll notice86
Nothing to try yet21
Under the hood125

Either side of it

v2.1.266Older
v2.1.268Newer

Open the release →

Names in this entry

cli--use-anthropic-git-proxy
--configure-git sets a commit identity and installs SSH commit signing backed by a code-sign subcommand.
envSELF_HOSTED_RUNNER_DRAIN_WAIT_MS
Self-hosted runner adds git URL-rewriting flags and an Anthropic-managed git auth option, plus a documented drain-wait timeout

Anthropic's note

Upstream's own release notes for v2.1.267 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Self-hosted runner: Changed --use-anthropic-git-proxy to be reported to the server at registration and to print a warning for each session that still clones through the legacy git proxy

Is this right?