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.
How sure we are
One source agreesOne thing we can check says the same as this entry.
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…
