Background worktree isolation now reads CLAUDE_BG_ISOLATION from a captured environment copy.
What's wrong with this entry?
The setting that decides whether background work runs in a separate worktree now reads CLAUDE_BG_ISOLATION from a captured copy of the environment rather than live process state. It still accepts worktree or none and otherwise falls back to the bgIsolation config value. A new comment documents how terminal recordings are addressed within a session folder.
keys.recording(projectKey, sessionId, stamp)
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.
-
v2.1.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task