Claude Code v2.1.310 · 23 Oct 2026
Self-hosted runners now report their capabilities
Self-hosted runners now send a capabilities list when they register and a capabilities header when fetching session settings; the orchestrator client sends an empty list
Under the hood Tier: how much it should matter to you
2 Useful: my rating, 1 to 5
3 Signal: worth watching, 1 to 5
Self-Hosted Runners Area: what it touches
Internal Changes Kind: in v2.1.310, 23 Oct 26
Internal Changes Section of the release
What
A self-hosted runner is a machine you run yourself to carry out remote Claude Code sessions. Runners now tell the server what they support.
When a runner registers, its request now includes capabilities .
When it fetches a session's remote settings, it sends an x-self-hosted-runner-capabilities header, a small label attached to the request.
The runner orchestrator client is created with capabilities: [], an empty list.
Why
This is a new field in how runners talk to the server. For now, the orchestrator client reports no capabilities.
See this entry in the whole of v2.1.310 →
23 Oct 2026 · 242 entries, this one is #148.
Use it now6 You'll notice128 Nothing to try yet8 Under the hood100
Open the release →
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 147 of 242
New remote switch for waiting on batches, off by default
Nothing to try yet Internals
In v2.1.310 Internal Changes release-page order
Next → · 149 of 242
Sandbox git and gh helper script gains relay and standalone modes
Under the hood Sandbox