Slow MCP tools are wired to appear as background tasks in interactive sessions.
The MCP call wrapper now carries a background-task handle, but nothing requests a task in this build.
What's wrong with this entry?
The MCP call wrapper now carries a background-task handle and the application state setter, so a slow MCP tool could show up as a task in an ordinary interactive session. Subagent calls and non-interactive sessions are excluded.
- The existing auto-background delay for MCP calls is passed alongside the new handle.
- Subagent calls are identified by the call carrying an agent id.
- The task pathway this feeds is not requested by anything in this build.
disallowTasks:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.