{"version":"2.1.295","anchor":"workflow-spawned-runs-are-never-backgrounded","canonical_anchor":"workflow-spawned-runs-are-never-backgrounded","heading":"Runs started by a workflow always stay in the foreground","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/workflow-spawned-runs-are-never-backgrounded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Runs started by a workflow always stay in the foreground\n\nAgents started by a workflow run can no longer be moved to the background\n\n**What**\n\nClaude Code can move some work into the background, so it keeps running while you carry on with something else. The check that decides this now also refuses when the work was started by a workflow run, so such runs stay in the foreground.\n\n**Why**\n\nAgents started by a workflow run stay in the foreground instead of being sent to the background.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}