{"version":"2.1.239","anchor":"voice-capture-says-why-it-actually-failed","canonical_anchor":"voice-capture-says-why-it-actually-failed","heading":"Voice capture says why it actually failed","tier":"notice","area":"Voice Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/voice-capture-says-why-it-actually-failed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Voice capture says why it actually failed\n\nA failed voice recording now shows the actual reason instead of \"no audio tool found\".\n\n**What**\n\nFailing to start a recording now shows the specific reason in the error toast instead of the fixed \"no audio tool found\" message.\n\n**Details**\n\n- Starting a recording returns a structured result carrying `started`, `superseded`, `expected` and a `hint`; the hint text is what surfaces in the toast and in the recorded voice error.\n- A start that is superseded by another while still connecting is now dropped silently rather than reported as a failure.\n\n**Evidence**\n\n`[voice] start superseded mid-connect; ignoring`\n\n- Area: Voice Mode\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}