Under the hood
Startup delays caused by managed-settings and MCP policy checks are now measured and recorded
What
Two 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.
Why
This gives visibility into how often and how long startup is delayed by these policy checks, which can help diagnose slow or stuck launches.