Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

GPTLiveModel: interrupting a turn while a tool is running leaves the call unanswered and the session stops replying

Chiusa
  • Qualcosa non va?
#7,679 7 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Li-john1021 ci sta già lavorando.

Dal 9/10/2026.

  • #7700 di @Li-john1021 — chiusa senza merge
  • #7753 di @longcw — chiusa senza merge
  • #7759 di @longcw — integrata

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
ai, audio-video-rtc

Direzione di ricerca

Start in the realtime generation task in livekit-agents/livekit/agents/voice/agent_activity.py (around lines 4608-4640), where interrupted turns commit only finished tool results, and trace how _backend_open_calls is populated and cleared. Follow the existing _interrupted_tool_output handoff path to see how an error output is produced. Done means an interrupted, still-running call receives exactly one output, function_tools_executed fires, and the session replies to the next question. Reproduce it with a delayed tool and session.interrupt(force=True) first.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Bug Description

With GPTLiveModel, if session.interrupt() is called while the voice model is still speaking its filler and a delegated tool call is running, that call never gets an output. On an interrupted turn, the realtime generation task only commits results of tools that already finished (code). For the tool that is still running, no FunctionCallOutput is produced, function_tools_executed is not emitted, and no response.item.create is sent. The call stays in _backend_open_calls, and from then on the session does not reply to the user at all.

#6785 made every call get exactly one output, but this case (a tool still running when the turn is interrupted) is still left without one.

Expected Behavior

The call is answered when the interrupted turn drops it (for example with an error output, as _interrupted_tool_output does for a handoff), so the conversation can continue.

Reproduction Steps
async def lookup_fee(product: str) -> str:
    await asyncio.sleep(8)
    return "The renewal fee is 1,480 yen."

model = openai.realtime.GPTLiveModel(responses_options={"model": "gpt-6-luna"})
session = AgentSession(llm=model)
await session.start(agent=Agent(instructions="Always call lookup_fee for prices.",
                                tools=[function_tool(lookup_fee)]))
# ask a price question; 0.5 s after the tool starts, while the filler is still playing:
session.interrupt(force=True)
# ~20 s later, ask another question

In voice tests:

  • interrupt during the filler while the tool runs: 4/4 runs never sent the tool output, and the second question got no reply (it was transcribed, but no server events came for ~35 s until close)
  • interrupt after the filler (agent thinking): 3/3 normal
  • interrupt a reply that has no tool call: 3/3 normal
  • same as the first case, then send a FunctionCallOutput for the open call 3 s later: 3/3 recovered and the second question was answered
Operating System

Windows 11

Models Used

GPT-Live (gpt-live-1) with a Responses backend (gpt-6-luna)

Package Versions
livekit==1.1.18
livekit-agents==1.8.3
livekit-plugins-openai==1.8.3
python==3.13

The code path above is unchanged in 1.8.5.

Additional Context

Our app calls session.interrupt(force=True) from error recovery and before a SIP transfer, so this can leave a phone call silent. Sending an output for the open call ourselves after the interrupt works around it.

Lingua principale
Python
Stelle
14.6k
Fork
3.9k
Merge medio
2g 23h
PR unite (30g)
177

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di livekit/agents

Tutte le issue di livekit/agents

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.