Group of 3 Under the hood
Subagent launches now report whether a request is foreground/background, non-interactive, and its workflow phase to telemetry
What
- Agent/task spawn telemetry now includes optional
workflowPhase,requestShape, andrequestNonInteractivefields when present. - A new helper computes
{requestShape, requestNonInteractive}for each subagent launch:requestShapeis'foreground'or'background'depending on how the subagent was launched, andrequestNonInteractiveis a boolean. These are captured at subagent launch time, propagated through to teardown, and merged into telemetry-adjacent objects in several places, including worktree teardown and subagent tool launch options. - Relatedly, another new helper scans queued messages for a
SubagentStarthook's additional context and for skill-loading metadata (isSkillLoadingMetadata), computinghookContextCarriedandcarriedPreloadsso hook context and preloaded skill state carry across resumed, skill-loaded turns.
Why This gives more detail in telemetry about how and why subagents are launched (foreground vs. background, interactive vs. not, and at what point in a workflow), and ensures hook context and skill preloads aren't lost when a subagent's turn is resumed after loading a skill.