Follow Discord
Sweep 01 Oct 2026 · 17:27Z Build v2.1.287 508 read Stable v2.1.285 Latest v2.1.287 Next v2.1.287 Feeds RSS JSON llms.txt llms-full.txt Unofficial
Reading a new release v2.1.288 First look · 1/6 0 findings $0.00 so far

Claude Code v2.1.274 ·

Inference token refresh rewritten with backoff, TTL tracking and refresh-on-error

Self-hosted runner's inference token refresh now uses jittered backoff, tracks token TTL, and refreshes immediately on a 401/403 instead of waiting

Group of 2 Under the hood Improvements
JSON All of v2.1.274
Under the hoodTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Self-Hosted RunnerArea: what it touches
ImprovementsKind: in v2.1.274,
ImprovementsSection of the release

What

  • The self-hosted runner's inference-token auto-refresh logic was rewritten. It now tracks the token's time-to-live (ttlMs, 30 minutes by default), and retries failed refreshes with exponential backoff plus jitter (a random delay) instead of a fixed interval.
  • Tokens nearing expiry get a separate, shorter retry window (expiredRetryMs).
  • A new error classifier distinguishes errors worth retrying from ones that aren't: a new RemoteConfigWithoutInferenceAuthError, or an HTTP 401/403, is treated as non-network and not retried early.
  • A new onResultApiError callback lets a 401/403 returned by the model API during a child session's turn trigger an immediate, out-of-band token refresh (refreshNow()) instead of waiting for the next scheduled refresh.

Why This makes token refresh more resilient to transient failures while reacting immediately to real auth failures, so a self-hosted runner recovers faster from an expired or rejected inference token instead of a child session stalling until the next scheduled refresh.

See this entry in the whole of v2.1.274 →

Feedback