{"version":"2.1.269","anchor":"new-settledat-tracking-on-server-response-settleawait-store","canonical_anchor":"new-settledat-tracking-on-server-response-settleawait-store","heading":"New settledAt tracking on server-response settle\/await store","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-settledat-tracking-on-server-response-settleawait-store","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New settledAt tracking on server-response settle\/await store\n\nClaude Code's internal async response tracker now records when each response was settled, not just its value\n\n**What**\n\nClaude Code has an internal store used to match up asynchronous responses from the server with the code waiting on them. That store now records a `settledAt` timestamp for each entry alongside the value it resolves to, with a new accessor to look up that timestamp.\n\n**Why**\n\nThis is internal bookkeeping; recording when a response was settled makes it possible to reason about timing (such as staleness or latency) for these async exchanges, though the finding doesn't show a specific new consumer of that timestamp.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}