The setup wizard spawns a detached runner into ./runner-setup and warns it outlives your session.
What's wrong with this entry?
The setup wizard's spawn tool starts a detached self-hosted runner process, defaulting its working directory to ./runner-setup/workspace, its log to ./runner-setup/runner.log and its pid file to ./runner-setup/runner.pid. Companion tools read http://127.0.0.1:<port>/healthz and /metrics on port 8080 by default (0 disables the listener). The permission prompt warns that the runner will keep running after this session ends.
- The spawn passes
--environment-secret-file,--capacity,--base-dir,--api-url,--health-portand--log-file. - The metrics tool reads only gauges prefixed
claude_code_self_hosted_runner_, skipping histogram buckets, per-session idle seconds and poll error totals. - Tail-log reads the trailing bytes of the log and redacts secrets before showing them.
- These tools are only available inside the setup and doctor wizards.
claude_code_self_hosted_runner_
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.225
Self-hosted runner checks its base directory before starting work
Both mention base self hosted runner