Follow Discord
Sweep 01 Oct 2026 · 17:27Z Build v2.1.287 508 read Stable v2.1.285 Latest v2.1.287 Next v2.1.287 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.286 ·

Background sessions that fail to start now say what blocked them

When a background session is blocked from starting, Claude Code now records whether a disclaimer or the folder trust check stopped it

You'll notice Improvements
JSON All of v2.1.286
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Background TasksArea: what it touches
ImprovementsKind: in v2.1.286,
ImprovementsSection of the release
What

A background session is a Claude Code session started with claude --bg that keeps working without you watching it. When one could not start because it was blocked, Claude Code used to report only that it was blocked. It now also gives the cause:

  • A disclaimer that has not been accepted.
  • The result of the workspace trust check, which asks whether you have agreed to trust the folder.

The trust check also no longer treats certain paths that reach the same place through a symlink (a file shortcut) as the same folder.

Why

Errors and usage reports for claude --bg can now name the exact reason a session was refused.

Read from
Names in the bundleclaude --bg
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 the symlink change to the trust check makes any difference you would see.
Anthropic's release notes agreeWindows: Fixed claude --bg and the agents view refusing a folder that claude already trusts when its trust record was saved with different…

See this entry in the whole of v2.1.286 →

Feedback