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
HomeReleasesv2.1.301entry #211

Claude Code v2.1.301 ·

A background-task check now looks at a different environment variable

A check that read CLAUDE_CODE_DISABLE_BACKGROUND_TASKS now reads CLAUDE_CODE_EXIT_AFTER_FIRST_RENDER and a different condition instead

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

Unclear It is not clear whether CLAUDE_CODE_DISABLE_BACKGROUND_TASKS still turns background tasks off or whether its check only moved elsewhere.

What

An environment variable is a setting you give a program from your shell. One check in Claude Code used to be true when any of these held:

The check in that same place is now true when CLAUDE_CODE_EXIT_AFTER_FIRST_RENDER is set or a different internal condition holds. Both variable names are still in the list of environment variables Claude Code recognises.

Why

If you use CLAUDE_CODE_DISABLE_BACKGROUND_TASKS to turn off background tasks, confirm that background tasks are still off after updating.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether `CLAUDE_CODE_DISABLE_BACKGROUND_TASKS` still turns background tasks off or whether its check only moved elsewhere.

See this entry in the whole of v2.1.301 →

Feedback