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

Credentials and transcript tails can be read through the storage backend

Credentials and transcript tails can be read from the new storage backend, but the flag is off.

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

Credential and transcript-tail reads sit behind tengu_hover_rest, off without a server value.

What

Stored credentials and the tail of a transcript being resumed can now be read and written through the alternative storage backend rather than directly from disk. Both are selected only when the tengu_hover_rest flag is on, which it is not without a server value, so this build uses the existing file paths.

Details
  • The credentials adapter wraps read, strict read, write and delete, and maps a refused symlink or a failed read to a single sentinel value. Writing still prints the same "Warning: Storing credentials in plaintext." notice as before.
  • Resume does a backend tail read plus a stat, allowing for a partially written last record, and falls back to reading the raw file with a warning if the read or the stat fails or the backend throws.
Evidence

Warning: Storing credentials in plaintext., hydrate tail: backend tail read failed

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

Read from
Names in the bundletengu_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.234: off

Read once, for one account on one subscription tier, against v2.1.234. 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 →

See this entry in the whole of v2.1.234 →

Feedback