Thanks — you're asking whether LiveKit has a concept of a "turn timeout." Short answer: yes — LiveKit Agents implements the behavior you’re asking about using a few related timeout parameters rather than a single parameter named exactly "turn timeout." What governs turn timeout behavior • min_endpointing_delay — minimum time (seconds) to wait after detecting silence before finalizing a user turn (default 0.5s). • max_endpointing_delay — maximum time (seconds) to wait for the user to resume speaking when turn-detector confidence is low (default 3.0s). • user_away_timeout — timeout (seconds) that marks a user as

away

after extended inactivity; this can be used to end a session or trigger prompts. How they work together • When voice activity detection (VAD) sees silence, the agent waits at least

min_endpointing_delay

before treating the turn as finished. • If a turn-detection model is used, the system dynamically adjusts the wait time between

min_endpointing_delay

and

max_endpointing_delay

based on model confidence. • If no user activity continues until

user_away_timeout

, the user is considered away and the system can close the turn/session or take other actions. If you want, I can: • Show where to change these values in your configuration. • Recommend sensible defaults for specific use cases (e.g., short Q&A vs. long multi-turn conversations). • Help debug unexpected behavior if your agent seems to be ending turns too quickly or waiting too long. Which of those would you like next, and are you using VAD-only or a turn-detection model? Sources: Turns overview | LiveKit Documentation | How to detect and handle silence during calls | LiveKit | Improving voice AI's turn detection with transformers | How does end-of-utterance detection work in conversations?