Dozens of write paths sit behind tengu_hover_rest, which reads false without a server value.
Dozens of places that save data now use the alternative storage backend only when the tengu_hover_rest flag is on, read once per process, and otherwise fall back to ordinary filesystem calls. Absent a server value the flag reads false, so this build writes to the filesystem as before. Files written through the new path get an explicit mode of 438 & ~process.umask(), or 384 for secrets.
- Affected save paths include job drafts and job deletion, daemon status, plugin config and marketplace manifests, PR status cache, org-memory discovery cache, facets, the paste store, agent metadata, workflow scripts, the closed-issue cache, forked-skill scoping, background dispatch, changelog migration, headless plugin installs, auth-required state, transcript history and REPL shutdown.
- Writes gained a
publishDisciplineoption with values"inPlace","atomic"and"followAtomic", replacing bare mode arguments in several places. - Plugin config reads gained an async backend variant alongside the existing synchronous one.
mode: 438 & ~process.umask(), publishDiscipline: "inPlace"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
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: 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
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.
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.