{"version":"2.1.221","anchor":"headless-mcp-startup-wait-reworked","canonical_anchor":"headless-mcp-startup-wait-reworked","heading":"Headless MCP startup wait reworked","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/headless-mcp-startup-wait-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Headless MCP startup wait reworked\n\nHeadless runs decide more carefully whether to wait for MCP servers before starting.\n\n**What**\n\nThe decision about whether headless startup waits for MCP servers moved into two dedicated helpers.\n\n**Details**\n\n- one helper reports whether an explicit MCP config asks the run to wait, returning true if any configured server is not of type `sdk`\n- the other computes a `deadlineMs` and a `localOnly` flag\n- `localOnly` is set for SDK-URL sessions that are not `CLAUDE_CODE_ENVIRONMENT_KIND === \"bridge\"` and not in coordinator mode\n\n**Evidence**\n\n`explicitMcpConfigRequestsWait`\n\n- Area: MCP\n- Names: `CLAUDE_CODE_ENVIRONMENT_KIND`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}