{"version":"2.1.242","anchor":"backgrounded-bash-commands-now-keep-a-task-awake","canonical_anchor":"backgrounded-bash-commands-now-keep-a-task-awake","heading":"Backgrounded Bash commands now keep a task awake","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/backgrounded-bash-commands-now-keep-a-task-awake","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Backgrounded Bash commands now keep a task awake\n\nWaiting on a backgrounded shell command now keeps a task alive, controlled by a remote setting defaulting on.\n\n**What**\n\nWork parked waiting on a backgrounded shell command is now treated as a live reason to keep the task alive, the same as waiting on a subagent, a monitor or a workflow. Killing a parked agent also cleans up shell tasks it left running. Controlled by the `tengu_concurrent_shore` remote setting, which defaults to on.\n\n**Details**\n\n- Previously only `agent:`, `monitor:` and `workflow:` waiters counted; `bash:` waiters now do too.\n- Absent any server value the fallback is true, so this is live in this build.\n\n**Evidence**\n\n`tengu_concurrent_shore`\n\n- Flag `tengu_concurrent_shore`: Not enough to say (read for one account on one subscription tier against v2.1.242; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}