hotato
GitHub

VFA-2026-0004

The agent starts speaking while the caller still holds the floor, cutting the caller off mid-utterance.

open1 independent reportlast reported 2026-07-25seen on livekit, openai-realtime

What this is

Filed as Agent interrupts caller, 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.

  1. soceviciuson GitHub issues2026-07-25livekitopenai-realtime
    Summary With an OpenAI Realtime RealtimeModel, syncing the chat context after an interrupted agent turn that has skipped (never-played) outputs throws Unsupported item type: agent_config_update. It is caught and...

    https://github.com/livekit/agents-js/issues/2115

    first seen 2026-07-25 · fetched 2026-07-25T16:04:52Z · body sha256 ab3e4acdc5db8206

  2. A reporton GitHub issues2026-07-25
    Withdrawn: collected in error: a pull request is a change somebody wrote, not an independent report of a call that went wrong.

    How a report comes down

    first seen 2026-07-25 · fetched 2026-07-25T15:09:07Z · body sha256 f9e4be9319bd5f61

  3. A reporton GitHub issues2026-07-25
    Withdrawn at the reporter's request.

    How a report comes down

    first seen 2026-07-25 · fetched 2026-07-25T02:05:12Z · body sha256 c7947049e6fa1993

  4. A reporton GitHub issues2026-04-20
    Withdrawn: collected in error: an automated account did not hear a caller, so this was never a report of a failure mode.

    How a report comes down

    first seen 2026-04-20 · fetched 2026-07-25T03:06:37Z · body sha256 0bfcdfa07fa60a9f

  5. A reporton GitHub issues2026-01-24
    Withdrawn: collected in error: a design proposal is a request for a thing to exist, not a report of a call that went wrong.

    How a report comes down

    first seen 2026-01-24 · fetched 2026-07-25T00:35:47Z · body sha256 0004506a7fe203e4

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 occurrence

The 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

  • The moment the agent began speaking while the caller still held the floor, and how far into the caller's utterance it landed.
  • Every threshold behind the call is printed with the finding and every frame is inspectable.

What your trace settles

  • Your own trace at that timestamp names the stage that decided to start: endpointing, the turn detector, or a barge-in setting.
bash
# Printed as TALK-OVER: the agent began talking while the caller still held the...
hotato autopsy ./call.wav

A shipped hotato subcommand maps to this mode, as detector kind agent_start_during_caller. Printed as TALK-OVER: the agent began talking while the caller still held the floor, reported with the overlap in seconds. Needs the caller and agent on separate channels. 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 GitHub

The record

Atlas id
VFA-2026-0004
Mode id
pat_a15a17a1fb34eb6f5b99cf59
Content digest
sha256:a15a17a1fb34eb6f5b99cf593991f9165660fe785613cdcc6dfbc1502b35f2e2
First reported
2026-07-25
Last reported
2026-07-25
First seen by the atlas
2026-07-24T23:15:54Z
Last re-checked
2026-07-25T15:24:52Z
Reported on
livekitopenai-realtime
Sources
GitHub issues
Scope
1 independent public report across 1 source. This entry states where the mode has been reported; where else it can occur is what the next report settles.

References

Every link this entry stands on: the post behind each report, and the artifact behind each status move.

  1. reporthttps://github.com/livekit/agents-js/issues/2115 · socevicius · GitHub issues · 2026-07-25

Machine surfaces

This entry, for an agent:feed.jsonfeed.atomfeed.schema.jsonatlas.llms.txt

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.