{"version":"2.1.265","anchor":"self-hosted-runner-session-exit-result-schema-added","canonical_anchor":"self-hosted-runner-session-exit-result-schema-added","heading":"Self-hosted runner session-exit result schema added","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/self-hosted-runner-session-exit-result-schema-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Self-hosted runner session-exit result schema added\n\nNew internal schema describes how a self-hosted runner's session ended, with phase, exit code, and signal\n\n**What**\n\nClaude Code now has an internal schema for describing how a self-hosted runner's session process ended. It records a `phase`, either `setup` (the process never started) or `run` (it exited), plus optional `exit_code` and `signal` values.\n\n**Why**\n\nThis gives more structured information about how and why a self-hosted runner session terminated, which should help in diagnosing failures that happen before versus after the session actually starts running.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}