{"version":"2.1.317","anchor":"api-metrics-no-longer-record-lasttokentime-at-response-end","canonical_anchor":"api-metrics-no-longer-record-lasttokentime-at-response-end","heading":"Response timing records no longer mark the last word at the end","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/api-metrics-no-longer-record-lasttokentime-at-response-end","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Response timing records no longer mark the last word at the end\n\nWhen output length is unknown, Claude Code no longer records when the last part of a reply arrived\n\n**What**\n\nWhen Claude Code does not know how many output tokens (the pieces of text the model produces) a reply had, it now records only the length of the reply. It no longer also records when the last piece arrived.\n\n**Why**\n\nThis may change how reply speed is measured.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}