{"version":"2.1.317","anchor":"self-hosted-runner-releases-finished-code-review-sessions-an","canonical_anchor":"self-hosted-runner-releases-finished-code-review-sessions-an","heading":"Self-hosted runners send their agent proxy URL and release finished code-review sessions","tier":"notice","area":"Self-Hosted Runners","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/self-hosted-runner-releases-finished-code-review-sessions-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Self-hosted runners send their agent proxy URL and release finished code-review sessions\n\nSelf-hosted runners pass agentProxyUrl to the server, park finished code-review sessions, and report their capabilities differently\n\n**What**\n\nA self-hosted runner is a machine you run yourself to carry out remote Claude Code sessions.\n\n- 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.\n\n- 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.\n\n- 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.\n\n**Why**\n\nRunners 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.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}