Flexible turn-taking control for Flux
By Steven Van ·
Flux now gives you full control over how turns end.
Deepgram announced Flexible turn-taking control for Flux on August 28, 2026.
What changed
Flux now gives you full control over how turns end. Beyond Flux's native end-of-turn detection, you can override it, suppress it entirely, or blend the two — and switch between these modes on the fly, even for a single turn, with a Configure message. Turn-taking goes from a fixed behavior to something you shape around each moment of a conversation. Three modes of turn-taking Automatic (default). Flux's native end-of-turn detection decides when a turn ends. EndOfTurn events carry "trigger": "model". Nothing changes for existing integrations. Semi-manual. Keep Flux's detection running, but override it whenever you have a definitive signal — a push-to-talk release, a DTMF tone, a "send" tap — by sending a ForceEndTurn. The model handles the ambiguous endings; you handle the unambiguous ones. Fully manual. Set eot_threshold=1.0 to suppress native detection entirely and own every turn boundary yourself, driving each ending with ForceEndTurn. Ideal when you already run your own VAD or endpointing stack. See Bring Your Own Turn Detection. Switch modes mid-stream — even per turn Because eot_threshold can be updated live with a Configure message, you can change turn-taking behavior for exac