You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Self-Hosted RunnersArea: what it touches
ImprovementsKind: in v2.1.309,
ImprovementsSection of the release
What
A self-hosted runner is a machine you run yourself that starts Claude Code sessions for the web. Sessions it recognises as a code review are now handled specially.
The runner refuses to start a code review when:
it is started with --debug-token-dir
it runs on Windows
--capacity is above 1
it cannot make itself non-dumpable, meaning protected from having its memory copied out
Otherwise the Claude Code process it starts for the review:
loads no user, project or local settings, so nothing from that machine's Claude Code config (it is started with an empty --setting-sources= and a filtered set of arguments)
gets no session token file
receives its session and inference tokens on file descriptors 4 and 5 (numbered channels opened by the parent process) instead of in its environment variables
The hook that runs after the session no longer receives the session access token for reviews.
Startup also gained a new condition that clears the setting sources, the same thing --restricted does. Before, only --restricted or one existing check did this.
Why
If you operate a self-hosted runner, code reviews will be declined on Windows, with --debug-token-dir, or with --capacity above 1. In the setups that do run them, tokens are kept out of the review process's environment and the machine's own Claude Code settings are not used.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed a skill in an --add-dir folder being unreachable when another skill already held its name; it is now offered as <folder>:<name>
