Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.234 Home All releases olderv2.1.233 v2.1.235newer
Claude Code v2.1.234

Storage backend writes are now pinned behind a flag and pass explicit file modes

Not switched on
Useful2 Signal4
Storage Backend Notable not in their notes

Saved data can route through a new storage backend with explicit file permissions, but the flag is off.

Dozens of write paths sit behind tengu_hover_rest, which reads false without a server value.

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: 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

tengu_hover_rest
What

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.

Details
  • 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 publishDiscipline option 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.
Evidence

mode: 438 & ~process.umask(), publishDiscipline: "inPlace"

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.

See this entry in the whole of v2.1.234 →