{"version":"2.1.286","anchor":"background-session-workspace-trust-and-gate-blocked-reasons","canonical_anchor":"background-session-workspace-trust-and-gate-blocked-reasons","heading":"Background sessions that fail to start now say what blocked them","tier":"notice","area":"Background Tasks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/background-session-workspace-trust-and-gate-blocked-reasons","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Background sessions that fail to start now say what blocked them\n\nWhen a background session is blocked from starting, Claude Code now records whether a disclaimer or the folder trust check stopped it\n\n**Unclear.** It is not clear whether the symlink change to the trust check makes any difference you would see.\n\n**What**\n\nA 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:\n\n- A disclaimer that has not been accepted.\n\n- The result of the workspace trust check, which asks whether you have agreed to trust the folder.\n\nThe trust check also no longer treats certain paths that reach the same place through a symlink (a file shortcut) as the same folder.\n\n**Why**\n\nErrors and usage reports for `claude --bg` can now name the exact reason a session was refused.\n\n- Area: Background Tasks\n- Names: `claude --bg`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}