{"version":"2.1.282","anchor":"new-intake-phase-timing-and-read-ahead-telemetry-on-enqueued","canonical_anchor":"new-intake-phase-timing-and-read-ahead-telemetry-on-enqueued","heading":"Queued messages record how long each step of taking them in took","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/new-intake-phase-timing-and-read-ahead-telemetry-on-enqueued","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Queued messages record how long each step of taking them in took\n\nClaude Code now logs a step-by-step timing breakdown for queued messages, plus whether a read-ahead option was on and used\n\n**Unclear.** It is not clear which setting switches the attachment read-ahead on.\n\n**What**\n\nWhen you send a message and Claude Code puts it in a queue to handle, the queued message now carries a breakdown of how long each step of taking it in took. The steps are:\n\n- before reading\n\n- removing duplicates\n\n- waiting for settings to settle\n\n- running the receive hook (a script you can set to run when a message arrives)\n\n- attachments\n\n- waiting to be admitted\n\n- the admission check\n\n- everything else\n\nThe usage report sent when a message is queued also gains two fields: whether a read-ahead option was switched on, and whether it was actually used.\n\n**Why**\n\nThis is measurement only and changes nothing you see. It suggests Claude Code is testing whether reading attachments ahead of time makes messages get handled faster.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}