The check for whether background commands are allowed has more conditions
Claude Code now decides whether background commands are off from a disable setting and another condition, with an exception when shells are kept elsewhere
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Background ShellsArea: what it touches
Internal ChangesKind: in v2.1.301,
Internal ChangesSection of the release
Unclear It is not stated what turns background tasks off, so whether background commands are available in a given setup is unclear.
What
Claude 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.
Why
This may change whether background commands are offered, including when Claude Code is being run as an MCP server.
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 stated what turns background tasks off, so whether background commands are available in a given setup is unclear.
