{"version":"2.1.265","anchor":"backgroundworkflow-agent-spawns-now-pass-description-and-wo","canonical_anchor":"backgroundworkflow-agent-spawns-now-pass-description-and-wo","heading":"Background\/workflow agent spawns now pass description and workflow phase context","tier":"internal","area":"Background Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/backgroundworkflow-agent-spawns-now-pass-description-and-wo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Background\/workflow agent spawns now pass description and workflow phase context\n\nBackground workflow agent spawns now carry a description and workflow phase\n\n**Unclear.** The finding doesn't say where this description\/phase or promptFramed value is surfaced to the user.\n\n**What**\n\nWhen Claude Code spawns a background agent as part of a workflow, the spawn call now includes `description` (taken from the agent's label) and `workflowPhase` (taken from the agent's phase). The progress updates sent for workflow agents also now include a `promptFramed` value.\n\n**Why**\n\nThis gives background workflow agents more context about which workflow and phase they belong to, which should make their progress and purpose easier to track.\n\n- Area: Background Agents\n- Names: `workflowPhase`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}