{"version":"2.1.269","anchor":"workflow-agent-spawns-now-wait-for-mcp-tool-sync-before-re","canonical_anchor":"workflow-agent-spawns-now-wait-for-mcp-tool-sync-before-re","heading":"Workflow agent() spawns now wait for MCP tool sync before resolving tools","tier":"notice","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/workflow-agent-spawns-now-wait-for-mcp-tool-sync-before-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Workflow agent() spawns now wait for MCP tool sync before resolving tools\n\nWorkflow agents now wait for MCP tool syncing to finish before their tool set is resolved\n\n**What**\n\nBefore a spawned workflow agent's set of available tools is computed, Claude Code now waits for MCP (Model Context Protocol, used for external tool integrations) servers to finish syncing, polling until they're ready or a maximum wait time elapses. This only applies in workflow contexts.\n\n**Why**\n\nThis prevents a workflow agent from starting with an incomplete tool set because MCP servers hadn't finished connecting yet.\n\n- Area: Workflows\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}