{"version":"2.1.309","anchor":"streaming-state-tracks-the-wait-for-the-main-response","canonical_anchor":"streaming-state-tracks-the-wait-for-the-main-response","heading":"Claude Code tracks the wait for a reply to its main request separately","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/streaming-state-tracks-the-wait-for-the-main-response","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Claude Code tracks the wait for a reply to its main request separately\n\nClaude Code now records when it is waiting for a reply to its main request and uses that to decide the request is under way\n\n**Unclear.** What, if anything, a user sees differently from this change is not clear.\n\n**What**\n\nClaude Code now keeps a separate record of the stretch between sending its main request to the model and the reply starting to arrive. It decides that the main request is under way when either that wait is in progress or the reply is already streaming in. Before, it used a general \"requesting\" state for the first half of that check.\n\n**Why**\n\nThe timing of status displays tied to a request starting could shift slightly.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}