Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.318 ·

Refresh-token expiry is clamped and its warning reworked

A login refresh can no longer push out refreshTokenExpiresAt, and the expiring-login warning now works from a validated date

Group of 2 You'll notice Improvements
JSON All of v2.1.318
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
AuthArea: what it touches
ImprovementsKind: in v2.1.318,
ImprovementsSection of the release

What

When you sign in, Claude Code gets a refresh token, a long-lived key it uses to get new short-lived access keys without asking you to sign in again. Refresh tokens can have an expiry time, refreshTokenExpiresAt, and the way it is handled changed.

  • On sign-in, the new expiry is used only if it is valid.
  • On refresh, the earlier expiry is kept and the sooner of the old and new times wins. If there was no valid earlier expiry, it is left unset. Before, the new value was taken if present, otherwise the old one.
  • The check that warns about an expiring refresh token now returns the expiry as a date instead of a count of days left, and validates it with a helper instead of a bare number check. The old code appeared to read a missing value.

Why

A refresh can no longer stretch the life of a time-limited login. The expiry warning may now show a date instead of a day count, and may work where it did not before.

See this entry in the whole of v2.1.318 →

Feedback