Your Voice Agent is Just a Walkie Talkie — Neil Zeghidour, Gradium
Read the talk
Your Voice Agent Is Just a Walkie-Talkie
Neil Zeghidour traces voice interfaces from rigid assistants to tool-using agents, then shows why fast speech-to-speech still feels unnatural—and how audio tokens, simultaneous streams, and a hybrid voice-plus-text architecture could fix it.
From a talk by Neil Zeghidour
At a glance
Ideas worth remembering
Open-ended dialogue, external action, expressive speech, low latency, and simultaneous conversation are distinct capabilities; improving one does not guarantee the others.
Speech-to-speech can remove the explicit text cascade, but a half-duplex system still alternates between listening and speaking. Backchannels therefore become unwanted turn changes.
Neural codecs and multi-stream modeling solve different problems: codecs compress long waveforms into audio tokens, while two streams represent simultaneous speech and silence for both participants.
Full duplex makes overlap resilient but does not guarantee good timing or strong reasoning. The early system could interrupt too often while remaining less capable than cascaded agents.
The hybrid proposal gives a small full-duplex model responsibility for conversational flow and delegates difficult reasoning and tools to a replaceable text backend. Its success depends on reliable delegation and asynchronous coordination.
Voice assistants first traded agency for conversational range
Gradium co-founder and CEO Neil Zeghidour frames voice-agent progress around capabilities that often get conflated: open-ended conversation, useful action, natural vocal expression, low latency, and the ability to listen while speaking. Gradium grew from voice research at Kyutai and trains audio foundation models for tasks including speech recognition, synthesis, translation, and spoken dialogue. The history matters because each generation improved a different part of the experience rather than advancing all of them together.
The 2011 Siri demonstration already contained real agency. A person could ask for the weather or the Nasdaq, and the assistant connected that utterance to an application action. Behind the voice, speech recognition produced a transcript; natural-language understanding classified the request, selected the application, and triggered a supported operation. This was a complex, closed-ended pipeline: useful inside its predefined territory, unable to roam far beyond it.
OpenAI’s original voice mode reversed that balance. An LLM replaced much of the hand-built dialogue logic, so a user could request a bedtime story about Larry, a hedgehog with sunflower petals instead of spines, and receive an improvised response. The system gained conversational breadth and more natural speech, but in Zeghidour’s comparison it lacked Siri’s ability to retrieve weather or market information and still took several seconds to answer. Open-ended dialogue and agency turned out to be separate features.
Three capabilities that evolved separately
Read the diagram as text
- Closed-ended assistant. Siri-era pipeline — Classifies a transcript, selects an application, and triggers a predefined action.
- Open-ended voice chat. Original voice mode — An LLM supports broad conversation but, in the example, does not recover external agency.
- Tool-using voice agent. Cascaded agent — A conversational model tracks state and invokes tools to perform a task.
- Closed-ended assistant → Open-ended voice chat: Gains conversational range; loses demonstrated agency.
- Open-ended voice chat → Tool-using voice agent: Restores action through tools, reasoning, and planning.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
A drive-through order shows what tool use adds—and what text removes
The drive-through demonstration develops the next step through one concrete order. The customer asks for a chicken sandwich, selects the classic option, asks what else is available, and adds mac and cheese. The observable change is persistent task state: after several exchanges, the agent can report that the order contains both items. Zeghidour says payment would follow, although the shown exchange stops before completing it.
The causal chain is straightforward: the system interprets each utterance, consults the menu, records the chosen sandwich, answers a category question, adds the side, and computes the current order. An LLM is no longer merely generating a conversational response; it participates in an agent equipped with tool calling, reasoning, planning, and task state. That recovers agency in a more general form than the original closed assistant.
The remaining weakness sits in the cascade: speech-to-text converts the voice into words, a text model reasons over those words, and text-to-speech generates a new voice. This architecture can use a strong text model and dependable tools, but every component adds delay. More subtly, the transcript flattens information that was present in the input audio—tone, emotion, hesitation, and other nonlinguistic cues. Speech-to-speech promises to preserve that information while reducing latency.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Backchanneling exposes the walkie-talkie underneath
A single speech-to-speech model can absorb the explicit speech-recognition, text-model, and speech-synthesis stages. In the advanced voice example, a person says he is nervous during a live demonstration and receives an immediate spoken response. Direct audio modeling can retain nonlinguistic information and deliver latency that Zeghidour considers already good enough. The cost, in his qualitative assessment, is that these speech-to-speech systems remain less capable than their text-based, cascaded counterparts; the talk does not present a benchmark for the size of that gap.
Speech-to-speech still does not imply full duplex. A half-duplex system divides the exchange into two states: the model speaks, or the model listens. That works until the listener contributes a brief “mm-hmm,” “yeah,” or “sure.” Humans use these backchannels to signal attention without asking for the floor, but a turn-taking system can interpret any incoming speech as an interruption.
The demonstration makes the failure visible. The model starts brainstorming, the user says “mm-hmm,” and the response stops. After the user explains that the acknowledgment was not an interruption, the model resumes—only to stop again at the next “sure.” Even the explicit lesson about backchanneling does not fix the exchange, because the failure is structural rather than instructional. The system must switch turns whenever it detects user speech.
That is the walkie-talkie problem. Faster turn changes can make half duplex feel responsive, but they cannot represent both sides speaking at once. Human calls include acknowledgments, interruptions, overlap, and moments when neither person speaks. Zeghidour says calls with a relative can contain simultaneous speech for up to 20% of the time; the talk supplies no measurement behind that figure, so it serves as an illustration of normal overlap rather than a quantified general rule.
Why low latency cannot repair half-duplex turn-taking
Read the diagram as text
- Listening. Half duplex — The model accepts user audio but does not speak.
- Speaking. Half duplex — Incoming speech forces a turn decision and may stop the response.
- Two simultaneous streams. Full duplex — Either participant can speak or remain silent independently.
- Listening → Speaking: Turn changes when the model begins answering.
- Speaking → Listening: Detected user speech yields or breaks the turn.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Raw waveforms are too long, so codecs turn audio into tokens
A text language model predicts the next token from earlier tokens. A speech model needs an analogous prediction target for audio, but a raw waveform is far longer than a sentence’s word sequence. Zeghidour’s example takes about three seconds to say and contains eight words. At 24 kHz, those three seconds contain 72,000 waveform samples: 3 × 24,000.
That length is prohibitive for ordinary transformer attention. Under the quadratic-cost relationship used in the talk, multiplying sequence length by 10,000 multiplies attention cost by 100 million. The 10,000 factor is a rounded illustration rather than the exact ratio between 72,000 samples and eight words, but it captures the scale problem: treating every audio sample like a language token makes the sequence astronomically expensive.
A neural codec, also called an audio tokenizer here, changes the representation. An encoder compresses the waveform into a dense sequence of learned audio tokens; the language model predicts over those tokens; a decoder reconstructs high-quality audio. Tokenization makes speech manageable for language-model training, but it does not solve duplex behavior. If user and system tokens are still placed one after another in a single sequence, the conversation remains turn-based.
How a waveform becomes modelable audio
Read the diagram as text
- Raw waveform. Audio domain — Three seconds at 24 kHz contains 72,000 samples.
- Neural codec encoder. Codec — Compresses audio into a dense learned representation.
- Audio tokens. Model domain — A language model can predict these abstract units from prior context.
- Neural codec decoder. Codec — Reconstructs high-quality audio from predicted tokens.
- Output speech. Audio domain — The decoded waveform becomes the model’s spoken response.
- Raw waveform → Neural codec encoder: Compress.
- Neural codec encoder → Audio tokens: Emit dense representation.
- Audio tokens → Neural codec decoder: Decode predicted units.
- Neural codec decoder → Output speech: Reconstruct waveform.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Full duplex requires two timelines, not one alternating sequence
Full duplex adds a second representation change. Instead of one token stream alternating between user and system, a multi-stream model represents both participants independently. At any instant, both may speak, both may be silent, or either one may speak alone. Overlap is no longer an exceptional event that forces a turn transition; it is an ordinary state in the model’s input and output.
The Moshi demonstration makes that relationship audible through a fictional spacecraft exchange. A person asks for a route, travel time, and mission readiness. The model sometimes anticipates the end of a question and begins answering before the speaker finishes. Crucially, simultaneous speech does not terminate the interaction. The demonstration establishes overlap handling and conversational timing, not actual trajectory calculation or verification of the ship’s supplies.
Full duplex brings its own behavioral problem: the early model interrupted too often. Zeghidour describes that as irritating, even while reporting that the conversation remained continuous through noise and coughing. Two streams make overlap survivable; they do not teach politeness or determine when anticipating a speaker is appropriate.
Natural flow also did not make the model capable enough for serious agent work. Zeghidour bluntly describes the early full-duplex system as less intelligent than speech-to-speech models that were already behind cascaded agents. Casual conversation may tolerate that. An agent entrusted with tool calls, planning, or transactions cannot give up reasoning merely to sound more human.
His explanation is finite model capacity. A text model adapted to speech must understand language, interpret audio, and generate audio using a fixed collection of weights. Those extra modality responsibilities consume capacity that could otherwise support reasoning. This is a proposed explanation for the observed tradeoff, not a measured law quantifying how many reasoning capabilities each audio feature costs.
One alternating stream versus two concurrent streams
Read the diagram as text
- User → system → user. Half duplex — Contributions occupy one sequence, so the conversation alternates turns.
- User audio stream. Full duplex — Can independently contain speech or silence.
- System audio stream. Full duplex — Can independently contain speech or silence at the same time.
- User audio stream → System audio stream: Modeled concurrently rather than concatenated.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Two paths forward: scale everything, or separate conversation from intelligence
The first path is to keep the system end to end and scale it: use a larger speech-to-speech model, better pretraining, and stronger post-training until its intelligence becomes sufficient for more tasks. The operational advantage is simplicity—a single model handles the interaction. The development disadvantage is that adapting a frontier text model to understand and produce audio is complex, slow, and expensive. Zeghidour speculates that a major provider follows this path but explicitly says he does not know its internal architecture.
The second path separates the voice interface from the brain. A small, potentially on-device full-duplex model maintains timing, overlap, and natural speech. When the conversation requires reasoning, tools, planning, or external knowledge, it delegates asynchronously to a background text model. A shared backend could serve many small voice interfaces and return text for them to express conversationally.
This hybrid depends on a difficult handoff: the small interface must know when it does not know. The talk identifies that requirement without explaining how uncertainty is detected, how delegation is trained, or how a delayed answer is reconciled with a conversation that may have moved on. Those coordination details determine whether the split feels natural rather than like a cascade wearing a better voice.
Zeghidour favors the split for two practical reasons:
- Cost: Ordinary small talk does not need a gigantic multimodal model capable of solving differential equations. A small interface can handle routine interaction and reserve expensive reasoning for requests that need it.
- Backend choice: Developers can replace the text model as better reasoning systems appear. A unified speech-to-speech product ties conversational behavior and intelligence to one provider and to a costly audio-adaptation cycle.
The closing bet is deliberately more demanding than an impressive demo. A viable voice agent must match the natural overlap of full duplex while remaining economically competitive and capable of the tool use available in today’s cascaded systems. The hybrid architecture is presented as Gradium’s route toward that combination, not as proof that the handoff, economics, and agent reliability have already been solved.
The hybrid voice-agent architecture
Read the diagram as text
- Live user audio. Conversation — Includes words, timing, acknowledgments, and overlap.
- Small full-duplex voice model. Interface — Maintains natural interaction and decides whether it can answer locally.
- Background text LLM. Intelligence — Handles reasoning, planning, tool calls, and other agent capabilities.
- Spoken response. Conversation — The voice interface expresses the result inside the ongoing conversation.
- Live user audio → Small full-duplex voice model: Continuous audio stream.
- Small full-duplex voice model → Background text LLM: Delegate asynchronously when needed.
- Background text LLM → Small full-duplex voice model: Return text result.
- Small full-duplex voice model → Spoken response: Continue or complete the conversation.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Resources
From the talk
The official AI Engineer page provides the recording, chapter navigation, and complete timestamped transcript for following the demonstrations.
Further reading
- Gradium: Solving voiceArticle
Background on Gradium’s audio-model approach, research lineage, supported speech tasks, and intended production applications.
Related talks
- Neil Zeghidour - Voice AI: when is the "Her" moment?
Extends the same full-duplex argument into latency, paralinguistic understanding, production controls, cost, privacy, and on-device synthesis.
- Beyond Transcription: Building Voice AI That Actually Understands Conversations
Explains speaker diarization and overlapping speech, adding another view of why a transcript alone cannot represent a real conversation.
- Why ChatGPT Keeps Interrupting You
Examines interruption and premature turn detection from the voice-agent orchestration side, complementing the talk’s model-architecture explanation.
Transcript & slides
Loading transcript and slides…