{"version":"2.1.296","anchor":"self-hosted-runner-governed-origin-check-telemetry-settings","canonical_anchor":"self-hosted-runner-governed-origin-check-telemetry-settings","heading":"Self-hosted runners check governed repository origins and report new stages","tier":"notice","area":"Self-Hosted Runner","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/self-hosted-runner-governed-origin-check-telemetry-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Self-hosted runners check governed repository origins and report new stages\n\nSelf-hosted runners now check governed repositories' origin, note pending settings, and report several new diagnostic stages\n\n**What**\n\nA self-hosted runner is the program that runs Claude Code sessions on machines you operate yourself. It gains new checks and new named stages in its diagnostics list:\n\n- `self_hosted_governed_origin_check`: the runner checks the origin of the governed repositories it manages. The origin is the address git records for where a repository came from. Results are reported as `not_upstream` or `read_failed`.\n\n- Settings-wait note: the runner adds a note to the session when its own settings are still waiting to arrive.\n\n- `self_hosted_move_reissue`, `remote_paste_splice` and `ccs_plugin_mcp` are new stage names in the same list. Only the names are visible so far.\n\n**Why**\n\nThis mostly matters to people who operate runners. The origin check tells you when a governed repository's origin is not the expected upstream address, or when it could not be read at all.\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}