You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
Internal ChangesKind: in v2.1.317,
ImprovementsSection of the release
What
A self-hosted runner is a machine you run yourself to carry out remote Claude Code sessions.
When agentProxyUrl is configured, the runner passes it to the server when it registers. It also adds it as agent_proxy_url when fetching a session from GET /v1/code/sessions/{id}/remote, which used to send no extra details.
When a session ends with its code review done, the runner asks the server to release it, retrying if needed, so it is parked on the server. New log messages cover a release that is declined or fails.
The runner reports what it can do differently. With an exec path set it reports nothing. Otherwise it reports the single-session capability plus one more. Before, it reported this only for a single-session runner with no debug token folder and no exec path.
Why
Runners behind a proxy now tell the server about it. Finished code-review sessions are handed back to the server instead of being left running, and what a runner registers as may change.
