{"version":"2.1.323","anchor":"backgrounding-refuses-when-profile-or-environment-service-is","canonical_anchor":"backgrounding-refuses-when-profile-or-environment-service-is","heading":"Moving a session to the background can now be refused up front","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/backgrounding-refuses-when-profile-or-environment-service-is","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Moving a session to the background can now be refused up front\n\nClaude Code checks that a needed service is available before backgrounding a session, and refuses with 'Couldn't start a background session' if not\n\n**What**\n\nA background session keeps working while you do something else. Before moving a session to the background, Claude Code now checks that the service it relies on is available. If the check fails, it refuses with \"Couldn't start a background session\". The exit dialog reports the refusal.\n\nPressing the left arrow to open the agents view is blocked in the same way, with a message that begins \"Cannot open agents\". Before, nothing was checked in advance, and a problem showed up only as a failed start.\n\n**Why**\n\nYou can now be refused when you try to background a session, and the message tells you why.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}