many-forest-60185
03/24/2026, 3:06 AMtall-airline-16756
03/24/2026, 3:06 AMtall-airline-16756
03/24/2026, 3:06 AMallow_interruptions=False prevents the agent from being automatically interrupted while speaking. The agent’s speech won’t be cut off by short user utterances.
• VAD still runs: Voice Activity Detection continues to run in real time and will mark frames as speech. Transcription and VAD events are still produced even when interruptions are disabled.
• Filtering small utterances: You can tune the behavior by using:
◦ min_interruption_duration — require a minimum detected speech duration (default 0.5s) before treating the audio as an interruption candidate.
◦ min_interruption_words — require a minimum number of transcribed words (used when STT is enabled) before allowing an interruption.
• Manual control: If you want absolute control, keep interruptions disabled and use the VAD/transcript stream to decide when to call session.interrupt() or handle.interrupt() yourself. That way you can ignore small utterances programmatically and only interrupt when your own rules are met.
When to use which approach:
• Use threshold tuning (min_interruption_duration / min_interruption_words) if you want simple, automatic filtering of very short/noisy utterances.
• Use disabled interruptions + manual interrupts if you need custom, application-specific logic (for example, ignore single-word backchannels but interrupt on certain keywords or longer phrases).
If you’d like, tell me:
• Whether you’re using STT/transcription alongside VAD.
• The kinds of utterances you want ignored (example durations, example words like “uh”, “mmhm”, “okay”).
With that I can recommend specific threshold values or example logic for when to call interrupt() manually.
Sources: examples/voice_agents | livekit/livekit_composite | DeepWiki | Turns overview | LiveKit Documentation | Uninterruptable Agent | LiveKit Documentation | Turn Detection for Voice Agents: VAD, Endpointing, and Model-Based Detectio..., with interactive elements