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.238 ·

Plaintext credential store gained an in-process cache

Plaintext credential reads could come from memory instead of the file, but only under off-by-default storage.

Nothing to try yet No documentation found In Development
JSON All of v2.1.238
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
InternalsArea: what it touches
In DevelopmentKind: in v2.1.238,
In DevelopmentSection of the release

An in-process credential cache with a generation counter is present but only applies when the v5 storage decision is on.

What

Reads of the plaintext credential store can be served from a cached snapshot held in memory rather than re-reading the file, with a generation counter and an explicit invalidation entry point. Every write, delete and failed read clears it. This only applies when the off-by-default v5 storage decision is on.

Details
Evidence

fromStoreCopy

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

Read from
Names in the bundleCLAUDE_CODE_HOVER_REST
Feature flag
tengu_hover_rest Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.238: off

Read once, for one account on one subscription tier, against v2.1.238. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns off for tengu_hover_rest, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_hover_rest, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_HOVER_REST

See this entry in the whole of v2.1.238 →

Feedback