{"version":"2.1.221","anchor":"subagent-frontmatter-mcp-servers-connect-through-the-shared-","canonical_anchor":"subagent-frontmatter-mcp-servers-connect-through-the-shared-","heading":"Subagent frontmatter MCP servers connect through the shared bounded dial","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/subagent-frontmatter-mcp-servers-connect-through-the-shared-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Subagent frontmatter MCP servers connect through the shared bounded dial\n\nA hung MCP server listed in an agent's frontmatter can no longer stall subagent startup.\n\n**What**\n\nMCP servers declared in an agent's frontmatter are connected through the shared dial helper with a timeout and abort signal, so a hung server can no longer stall subagent startup indefinitely.\n\n**Details**\n\n- previously the code awaited `connectToServer` directly with no bound\n- on timeout it logs a warning and returns no client\n- if the server entry was newly created, the connection is still cleaned up should it land after the timeout\n\n**Evidence**\n\n`subagent MCP server connect`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}