{"version":"2.1.319","anchor":"typed-mark-prompt-tracking-adds-a-retried-category-and-voi","canonical_anchor":"typed-mark-prompt-tracking-adds-a-retried-category-and-voi","heading":"Prompt tracking now counts retried messages and handles voice-call input","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/typed-mark-prompt-tracking-adds-a-retried-category-and-voi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Prompt tracking now counts retried messages and handles voice-call input\n\nClaude Code's tracking of typed prompts now keeps a separate list of automatic retry messages and treats voice-call input differently\n\n**Unclear.** It is not clear what this prompt record is used for, or how a reader would reach voice-call input.\n\n**What**\n\nClaude Code keeps a running record of the kinds of prompts in a conversation. Before, that record had four categories: typed text, commands, accepted suggestions and instructions. It now also has a \"retried\" category for messages sent automatically when Claude Code retries and continues on its own. These count toward the record's overall limit.\n\nInput that comes from a voice call is not collected as typed text. Messages from a voice call are also queued at a lower priority, so they are handled later rather than straight away.\n\n**Why**\n\nThe voice-call handling suggests that a way to talk to Claude Code by voice call is being built.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}