{"version":"2.1.269","anchor":"new-telemetry-policy-and-settings-cold-start-wait-outcomes","canonical_anchor":"new-telemetry-policy-and-settings-cold-start-wait-outcomes","heading":"New telemetry: policy and settings cold-start wait outcomes timed","tier":"internal","area":"Startup","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-telemetry-policy-and-settings-cold-start-wait-outcomes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New telemetry: policy and settings cold-start wait outcomes timed\n\nStartup delays caused by managed-settings and MCP policy checks are now measured and recorded\n\n**What**\n\nTwo startup steps that can block Claude Code from launching right away, the managed-settings wait during MCP (Model Context Protocol) policy cold start and a related wait for MCP policy limits, now record timing and outcome data through a shared tracker. Each wait is logged as one of: not started (`not_awaited`), timed out, or completed, along with when it happened.\n\n**Why**\n\nThis gives visibility into how often and how long startup is delayed by these policy checks, which can help diagnose slow or stuck launches.\n\n- Area: Startup\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}