Not switched on
Useful2 Signal0
Background MCP tasks could be parked and picked up by another session, but nothing creates them.
A second background-task protocol named sep2663 allows handoff to a helper process, with no code creating such tasks.
What's wrong with this entry?
Anonymous. No account, no email.
What
Background MCP tasks gained a second protocol variant, named sep2663, whose tasks can be parked and handed to a helper process so another session can pick them up. Nothing in this build creates such a task, so none of these paths currently run.
Details
- The stored task record rejects an oversized task id for this variant on read.
- The "is this task still running" check has a branch treating a parked task as owned by another session, by comparing the helper process's session id and project directory.
- The kill path aborts the drive controller, calls the variant's cancel hook, then waits on the helper write and deletes the task metadata with helper arguments.
- The only task constructor in the build accepts a protocol argument and its single caller does not pass one, and none of the helper fields or the parked flag are ever assigned, so every branch is unreachable.
Evidence
sep2663 task id exceeds the wire bound
Strings lifted out of the shipped bundle, so the claim above can be checked against them.