In this analysis
Correct interruption handling preserves the intended task across pauses, acknowledgements and explicit corrections.
Latency stopped being a sufficient demonstration
The Realtime API announcement of October 1, 2024 supplied an earlier milestone for interactive speech. GPT-Live followed on July 8, 2026, and GPT-Live-1 reached developers on September 10. Full-duplex interaction makes interruption handling a distinct acceptance problem. A voice agent can begin responding quickly and still misunderstand whether a hesitation means that the speaker has finished. Evaluating isolated question-and-answer clips misses the conversational boundary that the release sought to improve.
A pause is not an abandoned sentence
An illustrative learner says, “I would like to explain why,” pauses to think, and then continues. An assistant that immediately supplies the explanation may be fast while preventing the intended exercise. The relevant observation is whether the learner retains the conversational floor through a meaningful hesitation. That does not mean indefinite silence should always be preserved. The fixture needs both a thinking pause and an actually completed statement so that avoiding premature interruption cannot be achieved simply by never answering.
Acknowledgements and corrections have different consequences
A listener saying “right” during an explanation may encourage continuation. A listener saying “actually, use the other address” changes the task. Treating both as a command to stop would make the dialogue brittle; ignoring both would lose a correction. A useful evaluation includes these contrasting utterances within otherwise similar contexts. The expected behavior should describe the conversational consequence, such as continuing the explanation or revising its premise, rather than requiring an exact scripted phrase from the model.
Replayed audio needs a task outcome
A diagnostic packet can contain the audio, the intended interruption category, the evolving request and the eventual action record. Consider an illustrative delivery-address correction while the assistant is summarizing an order. The review asks whether the corrected address governs the final operation and whether the spoken summary reflects it. A transcript alone may conceal overlapping speech and timing; audio alone may conceal a wrong external action. Retaining both supports a more complete explanation of a failure without claiming that either artifact perfectly represents user intent.
A bounded claim about conversational quality
These fixtures are evaluation proposals, not observed performance results for GPT-Live-1. They explain why shorter response times cannot stand in for interruption correctness. A useful test set includes hesitation, acknowledgement, explicit correction and resumption of useful work, with clear expectations for each. The resulting evidence can separate an acoustic misunderstanding from a task-state error. That is a stronger basis for accepting a voice workflow than a polished demonstration in which every speaker politely waits for the previous sentence to end.