Managed settings could be read from cached storage instead of disk, but the backend is off.
A storage-backed managed-settings view with several safety bail-outs sits behind a default-off flag; setting the remote settings path env var skips it entirely.
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.235: on
Read once, for one account on one subscription tier, against v2.1.235. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Behind the tengu_hover_rest flag, which falls back to off, managed settings can be read from a storage-backed view that refreshes on updates instead of re-reading a file from disk. It stands down and returns to the disk probe if the watch fails, the cached copy is oversized, the cache file is a symlink, or the account changes mid-read. Setting CLAUDE_CODE_REMOTE_SETTINGS_PATH skips the priming entirely.
- The read is size-capped, and each stand-down is logged.
- Also in this change: permission helper entries armed from remote config are revoked if that arming is withdrawn while a command is running, and a status warning is shown for a remote entry that never ran.
Remote settings: storage view stood down (
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.236
write_dbcan send a document from a local JSON fileBoth mention path
-
v2.1.239
Backslashes in filenames are left alone on macOS and Linux
Both mention path
-
v2.1.246
An empty managed-settings tier can come from a host attestation
Both mention path