Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.287 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.287 ·

Self-hosted runners now pass the full /remote setup to session git rules

On self-hosted runners, session token updates now use the whole /remote setup and can add fetch rules for direct upstream repositories

Under the hood Internal Changes
JSON All of v2.1.287
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Internal ChangesKind: in v2.1.287,
Internal ChangesSection of the release
What

On a self-hosted runner, the step that refreshes a session's token now uses the whole /remote setup. A self-hosted runner is a machine you run yourself to carry out remote Claude Code sessions. Before this change, the step used only the push address and the token.

The change matters where governed git has direct upstreams. Governed git is the setup that controls how a session reaches git repositories. Direct upstreams are repositories the session connects to directly. In that case, the runner now builds fetch lines from the listed sources. It passes them to the session's git rules together with the push address and the token.

Why

Sessions on self-hosted runners with governed git can now have their fetch settings rewritten, as well as their push settings.

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 what the fetch lines do in a session.

See this entry in the whole of v2.1.287 →

Feedback