{"version":"2.1.274","anchor":"self-hosted-runner-now-surfaces-api-error-status-codes-from","canonical_anchor":"self-hosted-runner-now-surfaces-api-error-status-codes-from","heading":"Self-hosted runner now surfaces API error status codes from turn results","tier":"internal","area":"Self-Hosted Runner","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/self-hosted-runner-now-surfaces-api-error-status-codes-from","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Self-hosted runner now surfaces API error status codes from turn results\n\nSelf-hosted runner sessions now surface the API's numeric error status code when a turn fails\n\n**What**\n\nIn the self-hosted runner (used when running Claude Code sessions on your own infrastructure), when a turn result comes back marked as an error and includes a numeric API error status code, a new callback is now invoked with that status code.\n\n**Why**\n\nThis lets self-hosted runner integrations react to the specific API error status code behind a failed turn, rather than only knowing that a turn failed.\n\n- Area: Self-Hosted Runner\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}