{"version":"2.1.315","anchor":"turn-start-timing-schema-gains-phases","canonical_anchor":"turn-start-timing-schema-gains-phases","heading":"Startup timing breakdown now names four more phases","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/turn-start-timing-schema-gains-phases","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Startup timing breakdown now names four more phases\n\nClaude Code's breakdown of time spent before a turn's first request now names four more phases that used to be counted as other\n\n**What**\n\nClaude Code can report how long each part of a turn takes before its first request reaches the model. That breakdown now includes four more phases:\n\n- conversation append\n\n- init frame send\n\n- loop entry\n\n- request announcements\n\nBefore, this time was counted under \"other\", and older versions still count it there. This timing report is tied to the `CLAUDE_CODE_EMIT_STARTUP_TIMING` environment variable.\n\n**Why**\n\nIt gives a finer picture of where time goes when a remote session starts up.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}