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.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

Task storage gains an optional key-value store backend

Under the hood
Useful1 Signal2
Background Tasks

Task storage can run on a key-value backend instead of JSON files, but nothing uses it yet.

A key-value backend for task storage is wired in but every caller still uses per-task JSON files.

What

Task read, list, claim, update, delete and max-id helpers accept an optional store handle that replaces the per-task JSON files, but nothing in this build passes one.

Details
  • With a store present, tasks are enumerated via listEntries under a task namespace and read via readText, and deletion goes through the store using a keyed task path.
  • Locking switches to a separate .v5-lock-anchor path with an explicit lockfilePath.
  • Delete failures log the store's error code.
  • Plumbing only: every caller observed in this build supplies no store, so the file-based path remains in use.
Evidence

namespace: "task", [Tasks] Failed to delete task

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.221 →