{"version":"2.1.248","anchor":"name-a-self-hosted-runner-instead-of-using-its-hostname","canonical_anchor":"name-a-self-hosted-runner-instead-of-using-its-hostname","heading":"Name a self-hosted runner instead of using its hostname","tier":"use","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/name-a-self-hosted-runner-instead-of-using-its-hostname","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Name a self-hosted runner instead of using its hostname\n\nName a self-hosted runner with --client-label or an env var instead of using the hostname.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- The env var is trimmed and ignored if empty.\n- Registration passes the label alongside the account the runner is locked to.\n- The Prometheus-style identity line now carries `runner_id`, `version` and `client_label` together, so several runners on one host are distinguishable.\n- No feature flag; available to anyone running the self-hosted runner.\n\n**Evidence**\n\n`SELF_HOSTED_RUNNER_CLIENT_LABEL`, `--client-label`\n\n- Area: Self-Hosted Runner\n- Names: `--client-label`, `SELF_HOSTED_RUNNER_CLIENT_LABEL`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}