300ms endpointing cut off 22 percent of voice AI users mid-answer
speech_final marks silence, not the end of a thought.
300ms endpointing cut off 22 percent of voice AI users mid-answer
TL;DR
speech_final marks silence, not the end of a thought. At 300ms endpointing, 22 percent of users were cut off mid-answer. Raise the threshold before you start tuning prompts.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
Context: Postmortem by jiai on dev.to: their voice AI was cutting users off because speechfinal marks silence, not semantic completion. With endpointing at 300ms, 22 percent of users got cut off mid-answer. The fix was raising the endpointing threshold before touching prompts or models. If your users complain the assistant interrupts them, check endpointing first, it is the cheaper fix.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.