VFA-2026-0011
The agent's own synthesized speech bleeds into the audio input and voice-activity detection mistakes it for the caller starting to talk, triggering a false interruption.
What this is
Filed as Self-echo VAD false trigger, the name every report of this mode is collected under.
A failure mode is one named thing that goes wrong on a live call. This record carries every public report of it the atlas has found, in each reporter's own words, and a status that moves only when a re-check stores the artifact behind the move. Status open: reported and still open where it was reported.
Evidence
Every independent public report of this mode, newest first: who wrote it, where, when, what they said, and the link back to the post it came from.
...duplex audio: if you don’t subtract your own TTS audio (or at least gate VAD while TTS is playing), you’ll get false user-starts. Even a crude ‘TTS playing → raise...
https://news.ycombinator.com/item?id=46957802
first seen 2026-02-10 · fetched 2026-07-25T17:50:19Z · body sha256 7b3c299ade3943aa
Each quote is at most 30 words around the reported failure and links to the post it came from. If you wrote one of these and want it off this page, the removal path takes it down within 24 hours.
Hit this one yourself? Add your call to this entry: the stack, the versions, and what the caller heard. It lands as another independent report on this page, with your handle and a link back to what you wrote.
Report another occurrenceThe form is a GitHub issue on the hotato repo. Prefer email? [email protected] reaches a person either way.
What is measurable
Evidence tier: Tier 1 · dual-channel audio: caller and agent separated at capture, so overlap and timing are facts of the recording, exact to the sample.
What it establishes
- That the caller channel carries a lag-shifted copy of the agent's own audio, with the lag and the correlation printed beside the finding.
- This is an input-health check: it reads the recording you already have and reports what the channels contain.
What your trace settles
- Whether the loop is a room, a soft-phone, or an echo-cancellation setting is settled by your capture path; the check tells you the caller channel is carrying agent audio.
# Printed as a crosstalk line carrying the coherence and the lag: the caller channel... hotato trust --stereo ./call.wav
A shipped hotato subcommand maps to this mode, as detector kind echo_correlated_activity. Printed as a crosstalk line carrying the coherence and the lag: the caller channel looks like a lag-shifted copy of the agent's own audio, so the barge-in may be leaked output rather than a caller. hotato is MIT and runs locally. getting started.
Status history
A daily re-check reads every source thread on this page. The status moves when that re-check stores the link, the quote and the date behind the move, so every state on this record is one you can open.
The record has carried one status since it opened: open, reported and still open where it was reported. A move lands here with the link, the quote and the date that show it.
Discussion
Reader discussion of this mode: what fixed it, what did not, and what the record here is missing. It is a conversation, not part of the evidence above. The reports on this page are attributed and linked to their sources, and a comment is a comment.
Open this discussion on GitHubThe record
References
Every link this entry stands on: the post behind each report, and the artifact behind each status move.
- reporthttps://news.ycombinator.com/item?id=46957802 · PranayKumarJain · Hacker News · 2026-02-10
Machine surfaces
Removal
If you wrote something quoted on this page and want it gone, one email does it. The removal path takes the quote, the handle and the link off this page, out of the feeds and out of the llms.txt within 24 hours, and tombstones the id so the entry cannot quietly return at a new address.