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

Config saving reports success and detects compromised state

Config writes now report whether they actually succeeded, so a failed or compromised save isn't treated as done.

Under the hood Internal Changes
JSON All of v2.1.223
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
InternalsArea: what it touches
Internal ChangesKind: in v2.1.223,
Internal ChangesSection of the release
What

The locked config-write helper now tells its caller whether the write actually succeeded, which is what lets the machine id path avoid handing out an id it failed to persist.

Details
  • the helper returns a boolean instead of nothing
  • an onCompromised callback is passed into the lock and sets a flag
  • a no-op write is tracked separately, so an unchanged config still counts as success while a compromised lock does not
Evidence

{ onCompromised: () => (o = !0) }

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

See this entry in the whole of v2.1.223 →

Feedback