GPT-Bidi-1 is OpenAI's unreleased bidirectional voice model — internally codenamed "Maple" — that can listen and speak simultaneously. Unlike the current turn-based ChatGPT voice mode built on GPT-4o, Bidi-1 operates in full-duplex: you talk, it talks, and neither side has to wait for the other to finish. Think phone call, not walkie-talkie. Based on leaked code references, UI sightings, and audio samples that surfaced between June 16 and early July 2025, the model ships with three selectable intelligence tiers (Instant, Medium, High), handles mid-sentence interruptions, and appears capable of real-time multilingual translation.
None of this is officially confirmed by OpenAI. To help readers separate fact from inference, this article uses the following evidence grades throughout:
Grade | Meaning | Example |
|---|---|---|
Confirmed by leak | Directly visible in leaked code, UI strings, or audio samples from multiple independent sources | Model identifier |
Inferred | Logically derived from confirmed leaks combined with known engineering constraints, but not directly shown | Latency ranges per tier, end-to-end translation architecture, pricing estimates |
Speculative | Reasonable guesses with no direct evidence; included only where clearly labeled | Release date, API availability, chain-of-thought invocation in High tier |
Everything in this article traces back to community leaks, and I have applied those grades to each claim. Developers and power users should pay attention now, but calibrate confidence accordingly.
What Is GPT-Bidi-1?
"Bidi" stands for bidirectional. In telecommunications, full-duplex communication means both parties transmit and receive at the same time. Your phone calls work this way; current AI voice assistants do not.
The GPT-Bidi-1 model identifier first appeared in a code reference spotted by TestingCatalog on June 16, 2025 (confirmed by leak). Within the following week, the leak trail expanded rapidly: translation-related UI strings surfaced on June 23 (confirmed by leak), audio samples demonstrating emotional range appeared on June 24 (confirmed by leak), and by early July the model was a hot topic across Reddit's r/singularity and multiple X threads.
OpenAI has not published a blog post, API changelog entry, or press release about Bidi-1. The internal codename "Maple" was identified in at least three independent leak sources — Felo AI's analysis, KIE AI's deep dive, and Baidu Baike's encyclopedia entry (confirmed by leak across multiple sources). This level of cross-referencing gives the leaks more credibility than a single anonymous post, but treat all details as provisional until OpenAI confirms them.
GPT-Bidi-1 vs Current ChatGPT Voice Mode
The current ChatGPT Advanced Voice Mode runs on GPT-4o's audio capabilities and follows a turn-based protocol. You speak, the system processes your entire utterance, then it responds. If you interrupt, there is an awkward pause while the model discards its in-progress generation and starts over. Average round-trip latency sits around 300–500 ms in ideal conditions, but perceived delay feels longer because you must wait for your "turn."
GPT-Bidi-1 eliminates this structure entirely (confirmed by leak). In leaked demos, a user asked the model to count down from 10, then interrupted at 7 with a new question. The model stopped counting within approximately 200 ms and pivoted to the new topic without repeating earlier context. That 200 ms figure aligns closely with the ITU-T G.114 recommendation of sub-150 ms one-way mouth-to-ear delay for natural conversation — suggesting OpenAI is engineering toward telecom-grade responsiveness (inferred).
The practical difference is large. Turn-based voice feels like talking to an answering machine. Full-duplex voice feels like talking to a person. For anyone building voice-driven products — customer support bots, language tutors, accessibility tools — this is a structural change in what voice AI can do, not an incremental latency improvement.
Three Intelligence Tiers — Instant, Medium, and High
One of the most distinctive leaked features of GPT-Bidi-1 is a user-selectable intelligence tier system (confirmed by leak — the three-tier selector UI has been observed in leaked screenshots). The tier names — Instant, Medium, High — are confirmed. The specific latency ranges and internal mechanisms below are my estimates based on engineering constraints, not direct observations from leaks.
Instant Tier
Optimized for minimum latency. TTFB likely falls somewhere under 150 ms (inferred), competitive with human backchannel response times. From a product perspective, this tier probably exists for scenarios where acknowledgment speed matters more than depth: customer service quick-answers, simple Q&A, and casual conversation. Think of a fast-food drive-through order system — you need acknowledgment in under a second, not a philosophical treatise.
Medium Tier
The default balance point. TTFB probably falls in the 150–400 ms range (inferred) — still under the threshold where humans perceive conversational delay as unnatural. This tier would logically handle multi-turn reasoning, moderate context tracking, and everyday assistant tasks. For most users, this is likely the tier that "just works." The product rationale is straightforward: give the majority of users a good-enough default without requiring them to understand latency tradeoffs.
High Tier
Maximum reasoning power. TTFB could stretch to 500 ms or beyond (inferred). This tier may invoke heavier model weights or extended reasoning processes, though whether it uses chain-of-thought mechanics similar to o1-style models is unknown (speculative). The product case for this tier is clear: simultaneous interpretation, complex technical explanations, or scenarios where accuracy outweighs conversational flow. A conference interpreter, for example, typically operates with a 2–3 second ear-voice span — so even 1.5 seconds of model latency would be acceptable in that context.
No competitor currently offers user-selectable intelligence tiers for voice. Google's Gemini Live provides a single quality level; Gemini's multimodal approach is worth comparing if you are evaluating voice AI options across providers.
Mid-Conversation Interruption and Dynamic Adjustment
Handling interruptions sounds simple. It is not. Under the hood, the model must solve at least three concurrent engineering problems in real time.
Voice Activity Detection (VAD) must distinguish between the user starting a new utterance and background noise. Standard VAD algorithms trigger on energy thresholds, but in a full-duplex scenario where the model's own audio is playing back through the user's microphone, the system must simultaneously run acoustic echo cancellation (AEC) to subtract its own voice from the incoming signal. Even a 10 ms misalignment in the echo reference can cause false interruption triggers.
Then there is the state machine problem. In a turn-based system, the model has two states: listening or speaking. In full-duplex, it has at least four: listening-only, speaking-only, both-simultaneously, and transitioning. Each state change must update the context buffer, decide what generated tokens to discard, and determine whether the user's interruption is a true topic change or a backchannel signal like "uh-huh."
Leaked audio samples suggest Bidi-1 handles this well for pre-release software (confirmed by leak). In one clip, a user interrupted a factual explanation three times in 12 seconds, and the model correctly pivoted each time without losing the thread of the overall conversation. That is impressive engineering.
Real-Time Translation Capabilities
Leaked UI strings from June 23 reference language-pair selection interfaces and real-time translation toggles (confirmed by leak). If accurate, GPT-Bidi-1 would likely perform end-to-end speech-to-speech translation rather than the traditional pipeline of ASR (automatic speech recognition) to MT (machine translation) to TTS (text-to-speech) (inferred — the architecture is not confirmed, but an end-to-end approach is consistent with the latency targets implied by the tier system).
The traditional pipeline stacks latency at every stage. A typical ASR step adds 200–500 ms, MT adds 100–300 ms, and TTS adds another 100–200 ms. Total: 400–1000 ms before the first translated syllable reaches the listener. An end-to-end model collapses this into a single inference pass, potentially cutting total latency by 40–60%.
Quality measurement for this kind of system will eventually need frameworks like BLEU (for text fidelity) and COMET (for semantic adequacy), but the real-world benchmark is simpler: can two people who speak different languages hold a fluid conversation without feeling like they are on a satellite phone? No public evaluation data exists for Bidi-1's translation quality yet. Once it ships, expect the community to benchmark it aggressively.
Emotional Expression and Backchanneling
One of the most striking leaked audio samples featured GPT-Bidi-1 expressing what listeners described as genuine sadness (confirmed by leak — the audio clip was posted on June 24 and discussed across multiple forums) — not the flat, pleasant-but-empty tone that GPT-4o voice users have consistently complained about on X and Reddit.
This matters more than it might seem. Linguist Stephen Levinson's 2016 research established that human conversational turn-taking operates on an average gap of roughly 200 ms, and that backchannel signals — "mm-hmm," "okay," "right" — constitute 15–20% of all conversational turns. These are not interruptions. They are social glue that signals active listening.
Current ChatGPT voice mode does not produce backchannels. The result is a conversation that feels one-sided — you speak into a void, then the AI delivers a monologue. If Bidi-1 can generate contextually appropriate backchannels at natural timing intervals, it would represent one of the largest jumps in perceived naturalness since voice AI moved beyond robotic TTS.
Known Pain Points from Early Leaks
Not everything in the leaks is positive. Users who have interacted with early Bidi-1 builds have reported specific problems. These reports come primarily from X posts and Reddit threads; while I have identified the user handles and approximate dates, readers should note that these are informal social media reports, not structured bug reports or controlled tests.
"Responds Too Quickly" — The Counter-Intuitive Problem
User @SmokeAwayyy on X (late June 2025) reported that Bidi-1 "responds too quickly... fails to detect contextual pauses mid-sentence." In other words, if you pause to think for even a beat, the model interprets the silence as your turn ending and jumps in. This is the opposite problem from current voice mode's sluggishness, and arguably just as annoying. A possible fix would be a configurable pause-tolerance threshold, or a deliberate wait mechanism where the model holds back before responding.
Context Degradation in Long Conversations
User @real_aivy on X (early July 2025) noted that after 3–4 conversational turns, the model began repeating content from earlier in the session. @SmokeAwayyy separately observed that voice quality and speed degraded in longer conversations. Full-duplex streaming puts constant pressure on the context window — every millisecond of audio generates tokens that accumulate rapidly. Managing a large context window while simultaneously generating and receiving audio is an unsolved challenge at this scale.
Handling Long Pauses and User Silence
What happens when the user just stops talking? According to early feedback (sourced from the same X threads), Bidi-1 "sits there forever." There is no proactive re-engagement — no "Are you still there?" or "Would you like to continue?" This is the mirror image of the interruption problem, and solving it requires the model to maintain a timer-based state that can generate speech unprompted. Expect OpenAI to add a configurable toggle for this before public launch.
These pain points are the most differentiated part of the current leak picture. If you are evaluating Bidi-1 for production use, these are the failure modes to test for as soon as access becomes available.
Content Moderation and Privacy Considerations
Real-time streaming audio creates moderation challenges that text-based systems do not face. In a text conversation, the entire message arrives before the moderation classifier runs. In a full-duplex voice stream, content is generated and delivered continuously — meaning harmful content could reach the user before any classifier has time to flag it.
At a 16 kHz sample rate (standard for voice), Bidi-1 processes approximately 32,000 audio samples per second in each direction. Running a content classifier on this stream with less than 100 ms of added latency is non-trivial. OpenAI likely needs edge-deployed, lightweight classifiers rather than round-trips to a central moderation API.
GDPR and data residency add another layer. Continuous voice streams contain biometric data (voiceprints), which GDPR Article 9 classifies as "special category" data requiring explicit consent. Any enterprise deploying Bidi-1 in the EU will need to address where audio is processed, how long it is retained, and whether users can request deletion of voice data mid-conversation.
Pricing and Cost Estimates
OpenAI has not published any pricing for GPT-Bidi-1. The estimates below are entirely inferred from existing public pricing for GPT-4o audio and general assumptions about computational cost. Treat them as rough order-of-magnitude guidance, not predictions.
Current GPT-4o audio API pricing runs approximately $0.06 per minute of input audio and $0.24 per minute of output audio (as of mid-2025, per OpenAI's published rate card). Full-duplex processing roughly doubles the computational load — both directions are active simultaneously — suggesting a baseline in the range of $0.40–0.60 per minute for a Medium-tier Bidi-1 session (inferred).
The tiered structure likely means Instant is cheaper (perhaps $0.15–0.25/min) and High is more expensive (potentially $0.80–1.50/min) (speculative). These ranges could shift significantly depending on OpenAI's pricing strategy — whether they prioritize margin or market share.
For anyone tracking AI model costs across providers, comparing current pricing tiers helps calibrate what "expensive" actually means in this market.
Developer Integration — API, SDK, or ChatGPT-Only?
This is the question developers care about most, and the honest answer is: we do not know yet (speculative). The leaks suggest Bidi-1 will initially launch as a ChatGPT-integrated feature, not a standalone API endpoint.
LetDataScience raised the right question: will OpenAI offer server-side APIs for Bidi-1, or will it require embedded client-side SDKs that handle audio streaming locally? Full-duplex voice demands persistent WebSocket connections and real-time audio encoding/decoding, which is architecturally different from the current REST-based Realtime API.
If you are a developer planning voice features, here is what you can do now: familiarize yourself with OpenAI's existing Realtime API (currently in beta), build your audio pipeline with modular ASR and TTS components that can be swapped out, and monitor the OpenAI API changelog weekly. When Bidi-1 ships to the API, early movers who already have a working voice architecture will integrate in days rather than weeks.
GPT-Bidi-1 vs Google Gemini Live and Other Voice AI Models
Since all Bidi-1 data is from leaks, this comparison carries significant uncertainty. I have marked each cell's evidence basis below the table.
Feature | GPT-Bidi-1 (leaked) | Google Gemini Live | Hume AI EVI 2 |
|---|---|---|---|
Full-duplex | Yes ¹ | Yes ² | Yes ³ |
Intelligence tiers | 3 (Instant/Medium/High) ¹ | Single ² | Single ³ |
Mid-sentence interruption | Demonstrated in leaks ¹ | Supported ² | Supported ³ |
Emotional expression | Demonstrated in audio leaks ¹ | Limited ² | Core feature ³ |
Real-time translation | UI strings suggest yes ¹ | Available (40+ languages) ² | Not available ³ |
Backchannel signals | Evidence in leaks ¹ | Basic ² | Advanced ³ |
API availability | Unknown | Available ² | Available ³ |
Pricing | Estimated $0.15–1.50/min (speculative) | ~$0.04–0.07/min ² | ~$0.07/min ³ |
Source notes:
¹ Based on leaked code, UI strings, and audio samples (June–July 2025). Not officially confirmed.
² Based on Google's published documentation and Gemini API pricing page as of mid-2025. Gemini Live's full-duplex and interruption capabilities are documented in Google's developer blog posts.
³ Based on Hume AI's published API documentation and pricing page as of mid-2025. EVI 2's emotional expression capabilities are a core marketed feature per Hume's product page.
Google Gemini Live currently leads on price and availability. Hume AI leads on emotional intelligence. GPT-Bidi-1, if the leaks are accurate, would lead on flexibility (the three-tier system) and integrated translation. For a deeper look at Gemini's multimodal pricing, this guide breaks down the numbers.
Frequently Asked Questions
What does "Bidi" stand for in GPT-Bidi-1?
"Bidi" is short for bidirectional, meaning the model can listen and speak at the same time — full-duplex communication, like a phone call rather than a push-to-talk radio.
How is GPT-Bidi-1 different from the current ChatGPT voice mode?
Current ChatGPT voice mode is turn-based: you speak, it listens, then it responds. GPT-Bidi-1 operates in full-duplex, allowing simultaneous speech in both directions with natural interruption handling.
When will GPT-Bidi-1 be officially released?
No official date has been announced. Leak timelines suggest active internal testing as of June 2025, with code references and audio samples appearing in quick succession. A reasonable estimate is Q3–Q4 2025, but this is entirely speculative.
How can I try GPT-Bidi-1 early?
There is currently no public access channel. Monitor the ChatGPT mobile app for feature flags, watch the OpenAI API changelog, and follow @TestingCatalog on X for the latest leak tracking.
What languages does GPT-Bidi-1 support? Can it translate in real time?
Leaked UI strings reference language-pair selection menus, strongly suggesting multilingual support and real-time translation (confirmed by leak). Specific language counts have not been confirmed.
What are the practical use cases for bidirectional voice AI?
Key scenarios include real-time customer support (no hold-music dead air), simultaneous interpretation for multilingual meetings, voice-first accessibility tools for visually impaired users, language learning with natural conversational flow, and hands-free technical support in industrial environments.
Final Recommendation
GPT-Bidi-1 represents a notable architectural change in voice AI. The three-tier intelligence system — if it works as leaked — would give developers meaningful control over the latency-quality tradeoff that no competitor currently offers. The early pain points (over-eager responses, context degradation, silence handling) are real but characteristic of pre-release software and likely addressable before a public launch.
My recommendation: do not wait for the official launch to prepare. If you are building any product that involves voice interaction, start prototyping with OpenAI's existing Realtime API now. Build your audio pipeline to be modular — swappable ASR, TTS, and dialogue management components. When Bidi-1 ships, you want to be in a position to drop it in as a replacement, not start from scratch. The teams that treat this as a signal to start building will have a meaningful head start over those that wait for an official announcement.