Credentials and transcript tails can be read from the new storage backend, but the flag is off.
Credential and transcript-tail reads sit behind tengu_hover_rest, off without a server value.
tengu_hover_rest Off in both readingsThe 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: on
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's wrong with this entry?
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.
- 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.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.238
CLAUDE_CODE_HOVER_RESTgives a local override for the new credential and settings storageBoth mention hover rest
-
v2.1.238
The v5 storage choice reads the environment variable first
Both mention hover rest
-
v2.1.238
Plaintext credential store gained an in-process cache
Both mention hover rest