You'll notice
Useful2 Signal2
MCP background tasks are hard-blocked for subagents and non-interactive runs, with no setting.
What's wrong with this entry?
Anonymous. No account, no email.
What
Where the MCP task pathway exists, it is hard-blocked whenever the tool call comes from a subagent or from a non-interactive session. There is no setting; the block is wired into the call itself.
Details
- Task polling now cancels the task on the server if the local record stops being in the running state.
- The temporary files an MCP task writes alongside itself are cleaned up when it is cancelled.
- The pathway that these rules govern is not requested anywhere in this build.
Evidence
j.options.isNonInteractiveSession
Strings lifted out of the shipped bundle, so the claim above can be checked against them.