{"version":"2.1.301","anchor":"background-tasks-disabled-check-is-more-nuanced","canonical_anchor":"background-tasks-disabled-check-is-more-nuanced","heading":"The check for whether background commands are allowed has more conditions","tier":"internal","area":"Background Shells","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/background-tasks-disabled-check-is-more-nuanced","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### The check for whether background commands are allowed has more conditions\n\nClaude Code now decides whether background commands are off from a disable setting and another condition, with an exception when shells are kept elsewhere\n\n**Unclear.** It is not stated what turns background tasks off, so whether background commands are available in a given setup is unclear.\n\n**What**\n\nClaude Code can run shell commands in the background, letting them keep going while Claude does other work. The check for whether this is turned off used to depend only on whether Claude Code was running as an MCP server for another program. It now looks at whether background tasks are disabled, plus a second condition. A related check also makes an exception when background shells are kept elsewhere. Claude Code now records use of background commands when it runs as an MCP server.\n\n**Why**\n\nThis may change whether background commands are offered, including when Claude Code is being run as an MCP server.\n\n- Area: Background Shells\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}