Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.247 ·

Login credentials are re-read only when the keychain entry actually changed

Your login token is re-read from the keychain only when it genuinely changed, not on every check.

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

The cached OAuth token is now held per host alongside the last credentials modification time, credentials version and last keychain access token, so a change check that cannot read a version falls back to comparing the keychain token itself and only invalidates the cache when it genuinely differs.

Details
  • Replaces a set of memoized functions cleared piecemeal with a single per-host object exposing clear() and resetChangeCheck().
  • The object also holds the in-flight fetch promise, so concurrent callers share one refresh.
Evidence

lastKeychainAccessToken

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.247 →

Feedback