Waiting on a backgrounded shell command now keeps a task alive, controlled by a remote setting defaulting on.
tengu_concurrent_shore Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.242: off
Read once, for one account on one subscription tier, against v2.1.242. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Work 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.
- Previously only
agent:,monitor:andworkflow:waiters counted;bash:waiters now do too. - Absent any server value the fallback is true, so this is live in this build.
tengu_concurrent_shore
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task