{"version":"2.1.299","anchor":"runner-trust-of-canonical-prewarm-now-depends-on-an-ownershi","canonical_anchor":"runner-trust-of-canonical-prewarm-now-depends-on-an-ownershi","heading":"Self-hosted runners trust a prewarmed setup in fewer cases","tier":"notice","area":"Self-Hosted Runner","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/runner-trust-of-canonical-prewarm-now-depends-on-an-ownershi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Self-hosted runners trust a prewarmed setup in fewer cases\n\n`CLAUDE_RUNNER_TRUST_CANONICAL_PREWARM` now also needs a matching owner value, or the runner cleans up anyway\n\n**Unclear.** What the owner value is and how to set it is not stated.\n\n**What**\n\nA self-hosted runner is a machine you run yourself to carry out Claude Code jobs. Setting `CLAUDE_RUNNER_TRUST_CANONICAL_PREWARM` lets it trust a setup prepared in advance and skip cleaning it.\n\nBefore, that worked when the variable was true and `SELF_HOSTED_RUNNER_DRAIN_GRACE_MS` was 0. It now also needs an owner value that is either \"none\" or matches the caller's. If it does not, the runner logs a warning that the setting was ignored and cleans the setup anyway.\n\n**Why**\n\nIf you run self-hosted runners with this setting, the skip may now apply less often, and you may see the warning in your logs.\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: yes"}