Source Intelligence
Follow Discord

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.223 Home All releases ←olderv2.1.222 v2.1.224newer→
Claude Code v2.1.223

Background job state and roster writes can route through the v5 storage backend

Not switched on
Useful2 Signal3
Background Jobs Notable

Background job files can be stored somewhere other than disk, but nothing switches that on yet.

Job state, sidecar and roster writes have a storage-backend branch with versioned keys; with no backend supplied the filesystem path runs unchanged.

What

Job state.json, the order/stateOrder/group sidecars and the roster orphan-adoption write each gained a branch that goes through a storage backend object instead of the filesystem, using versioned keys, ifAbsent preconditions and size caps. Filesystem behaviour is unchanged when no backend is supplied, and what turns the backend on could not be determined from source.

Details
  • covers job state reads and writes, the three sidecar files, and the orphan-adoption seed write
  • failures on the backend path emit new warn-level diagnostics rather than throwing
  • when no backend object is handed in, the original filesystem path runs untouched
Evidence

[jobs] v5 state write 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.

See this entry in the whole of v2.1.223 →