Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.221 ·

Background-attach outcomes are journaled to disk and recovered later

Background session attaches now write a small journal file so crashed attaches still report what happened later.

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

Every background attach writes a journal file so an attach that dies with its process still reports an outcome on a later run.

Details
  • JSON journal under an attach-journal directory, created with mode 0700 and files 0600, deleted on completion.
  • Updated as milestones land: marksExpected, daemonBooted, interactiveReached, attachMs, msgsLoaded, msgsInJsonl, msgsRenderedAtFirstPaint.
  • On a later run, orphaned journals whose owning process is gone, or older than 24h (15 min for live pids), are claimed and replayed as synthetic tengu_bg_attach_outcome events carrying journal_recovered.
  • Windows rename and unlink contention gets 4 retries; files that still cannot be unlinked are renamed with a .cleared suffix.
Evidence

journal_recovered

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

Feedback