Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.321 ·

Background jobs no longer recreate their folder after it has been made once

Once a background job's folder exists, or after a relaunch following a stall, Claude Code now expects the folder to exist instead of creating it again

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

A background job is a task Claude Code keeps running on its own. Each job has a folder. Claude Code used to create that folder every time it launched the job. Now, once the folder has been made, or after the job has been relaunched because attaching to it stalled, Claude Code requires the folder to already exist instead of creating it.

Why

A job folder that was removed is no longer quietly recreated when the job is relaunched.

Read from
Feature flag
tengu_bg_settled_crash_restart Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.321: on

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.321. It isn't a statement about your account. What a flag value here can and cannot tell you

See this entry in the whole of v2.1.321 →

Feedback