{"version":"2.1.319","anchor":"self-hosted-runner-handles-refused-inference-token-renewal","canonical_anchor":"self-hosted-runner-handles-refused-inference-token-renewal","heading":"Self-hosted runners warn when the server keeps refusing model access","tier":"notice","area":"Self-Hosted Runner","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/self-hosted-runner-handles-refused-inference-token-renewal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Self-hosted runners warn when the server keeps refusing model access\n\nA self-hosted runner now posts a warning after 5 refused renewals of model access, and a notice when renewal works again\n\n**What**\n\nA self-hosted runner is a machine you run yourself that hosts Claude Code sessions. Its access to the model has to be renewed from time to time. Claude Code now counts clear refusals of that renewal.\n\n- After 5 refusals, it posts a warning in the session: \"The server has refused to renew this session's access to the model\"\n\n- When a renewal later works, it posts a notice saying the server renewed the session's access\n\n- After a refusal, it tries to renew again sooner than before\n\n**Why**\n\nIf access stops renewing, people running self-hosted runners now see it in the session instead of the session failing silently.\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}