Name a self-hosted runner with --client-label or an env var instead of using the hostname.
What's wrong with this entry?
The self-hosted runner accepts a client label via the SELF_HOSTED_RUNNER_CLIENT_LABEL environment variable or the new --client-label flag. Without one it falls back to the machine hostname. The value is registered with the runner and appears as client_label on the claude_code_self_hosted_runner_info metric.
- The env var is trimmed and ignored if empty.
- Registration passes the label alongside the account the runner is locked to.
- The Prometheus-style identity line now carries
runner_id,versionandclient_labeltogether, so several runners on one host are distinguishable. - No feature flag; available to anyone running the self-hosted runner.
SELF_HOSTED_RUNNER_CLIENT_LABEL, --client-label
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.229
Runner refuses unsafe client platform labels
Both mention client self hosted runner
-
v2.1.234
Self-hosted runners report when warm-up finished
Both mention self hosted runner
-
v2.1.236
Self-hosted runner releases a session only after its work finishes
Both mention self hosted runner