{"version":"2.1.288","anchor":"turn-request-timing-adds-three-phases","canonical_anchor":"turn-request-timing-adds-three-phases","heading":"Turn timing data adds three more phases","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/turn-request-timing-adds-three-phases","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Turn timing data adds three more phases\n\nTiming data for the start of a turn now includes message_prep, model_config_wait and auto_mode_context_wait\n\n**What**\n\nTiming data for the start of a turn now includes three more phases:\n\n- `message_prep`\n\n- `model_config_wait`\n\n- `auto_mode_context_wait`\n\nBefore, the timings went straight from the memory step to the compaction and query setup steps. This data is reported in remote sessions (where `CLAUDE_CODE_REMOTE` is set) and on hosts that set `CLAUDE_CODE_EMIT_STARTUP_TIMING`.\n\n**Why**\n\nThis is timing data only and does not change how Claude Code behaves.\n\n- Area: Telemetry\n- Names: `CLAUDE_CODE_EMIT_STARTUP_TIMING`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}