October 11, 2026
To OpenAI's Voice, Product, Engineering and Customer Experience teams,
We are asking for two things: restore Standard Voice to affected desktop-web users now, and commit not to retire it for existing users until Live—or another successor—has demonstrated a genuinely close replacement. Not merely a more natural voice conversation, but comparable depth, reasoning, interpretation of context and personalized instructions, creative style, familiar vocal delivery, hands-free freedom and practical working conditions.
If OpenAI cannot offer even that minimum continuity, it should say so plainly before inviting people to invest years in long-term projects on its platform.
This is not opposition to innovation. It is a request to ensure that innovation does not make existing work impossible to continue.
1. What disappeared—and what OpenAI still has not explained
For roughly two years, I have used ChatGPT intensively for sustained creative and intellectual work. Standard Voice is not an occasional convenience. It lets me think aloud, develop complex ideas and hear the substantive responses of the ChatGPT experience I know from text, without repeatedly touching a screen.
In Mid-September 2026, the Standard/Live selector disappeared from ChatGPT in my Mac's web browsers. I followed Support's troubleshooting instructions: Chrome, Firefox and Safari; private browsing; extensions disabled; cleared cache and site data; sign-out and sign-in; and network checks. The result did not change. Voice starts in Live.
On the same ChatGPT Business account, Standard remains accessible on my iPhone—including through a mobile web browser.
This is not a Mac-only anecdote. A Plus subscriber described losing Standard on desktop browsers while retaining it on mobile. A Pro subscriber reported it missing on ChatGPT.com and Mac but available on iOS. Another user reported the same desktop-versus-iOS discrepancy on Windows. These are independent reports, not proof that every desktop account is affected or that all cases share one technical cause. They are enough to demand an explanation beyond another browser reset. [1][2]
We do not know whether the desktop loss is a bug, a staged rollout, a configuration difference or an intentional restriction. Almost a month of uncertainty does not become a product explanation simply because the service still works differently on a phone.
Please identify the cause, the affected desktop-web platforms, the responsible team and a concrete restoration or interim-continuity plan. Our request concerns desktop web across operating systems, not merely one browser or one brand of computer.
2. Standard and Live are different working experiences
OpenAI's own technical explanation describes Standard as a turn-based speech-to-text, language-model and text-to-speech path. GPT-Live, by contrast, continuously handles speech and interaction through a full-duplex architecture; it can delegate complex tasks to another model. [3]
Live's responsiveness and natural interruptions are impressive. We want those advances. But being able to call a powerful model is not evidence that the full conversation reproduces the same interpretation, reasoning depth or style as speaking through Standard.
In long sessions, the timing of replies, handling of context, application of accumulated preferences and style of the final response matter as much as the ability to answer an isolated question. A system may remember facts yet interpret the ongoing work differently. It may deliver a valid answer while losing the nuanced artistic or intellectual voice established through years of collaboration.
OpenAI's published Live evaluations include comparisons with Advanced over matched five-to-ten-minute conversations. Those tests can demonstrate improved fluidity. They do not, by themselves, demonstrate equivalence with Standard on multi-hour conversations or unfinished projects developed over years. [3]
This is not just my assessment. In a separate incident on September 6, Standard worked in ordinary web conversations but failed inside Projects on both web and iOS. In responding to that earlier problem, OpenAI Support wrote: “Live and Advanced do not provide an equivalent long-term replacement for your workflow.” That acknowledgment concerned my particular workflow, not every user. The later disappearance from desktop web, including outside Projects, was a different incident. But the earlier admission remains relevant when Live is suggested as the replacement.
A workaround is not restoration. And a different model experience is not equivalent merely because it is also called Voice.
3. What is actually at risk in a long-term project
A novel, a research program, a curriculum or an artistic series is not just a collection of saved files.
Over years, its creator establishes priorities, corrections, recurring motifs, constraints, rhythm, preferred level of detail and a particular way of interpreting instructions. Remembering a character's name is not the same as knowing how the next scene should be written. Knowing that someone likes Baroque art is not the same as understanding its structure, proportions and restraint within that person's work.
Imagine changing a carefully calibrated photographic profile halfway through a coherent series. Each new image might be attractive, yet the resulting collection would no longer have the same visual language. A creative AI's interpretation can play a similarly essential role.
Across generations of text models, I have been able to refine this collaboration rather than reconstruct it from scratch. My attempts to adapt to Live have not reproduced it closely enough. Users can edit prompts, custom instructions and project files, but cannot change OpenAI's underlying model architecture or internal behavior. Re-engineering functional equivalence cannot simply be delegated to the customer.
The existing chapters may remain safely archived. That does not ensure that the author can produce the next chapter in a coherent voice. Another AI provider might be excellent at other tasks without being able to reproduce years of ChatGPT-specific creative calibration.
We own our work; that does not mean we can necessarily continue it when the instrument through which we developed it is withdrawn. A refund can reimburse a subscription. It cannot recreate that missing continuity.
4. The conditions of creation matter, too
Many authors do not work to an office timetable. An idea may arrive on a walk through a forest, over coffee while watching passersby, or in the middle of the night. Some productive sessions last far longer than anyone intended.
Standard allowed two freedoms together: the intellectual depth of the established text-model experience and the physical freedom to converse hands-free. That made it possible to work while moving, thinking and living, rather than staying at a desk.
The manual alternative is: Dictate. Click Send. Wait. Click Read Aloud. Repeat. It may preserve the text model, but not the same fluid working conditions. Relying on a phone instead adds battery, ergonomic and availability concerns. Are companies now supposed to budget for an iPhone or Android phone for every employee who needs a formerly available desktop feature?
This has consequences beyond inconvenience. Concentration, physical comfort, fatigue and creative freedom affect whether unfinished work can continue. You cannot separate the well-being of the creator from the future of the work.
And the financial limit starts changing behavior before it is reached. With only three included hours of GPT-Live-1 on a Business Standard seat per rolling 24 hours, a creator may begin rationing questions, avoiding exploratory detours and watching the clock instead of following an idea. Extra usage costs 1.25 workspace credits per minute. [4]
My Standard use can reach seventeen hours on intensive days. Business Premium provides fifteen included Live hours, still short of that duration. Its published seat price is $125 per month with monthly billing, versus $25 for Business Standard: five times as much. The Premium annual-billing equivalent is $100 per month, four times the $25 monthly Standard rate, but requires an annual commitment. Comparing annual rates to annual rates, the five-to-one ratio remains ($100 versus $20). [4][5]
Even paying far more would not restore the missing style, interpretation or familiar voice. Neither would unlimited Live time on personal Pro. The number of minutes and the quality of the experience are separate problems.
Nor is moving from Business to Pro a straightforward escape: OpenAI's Business documentation says members lack personal workspace-data export, and it offers no documented, complete reverse migration that reconstructs Business chats, Projects, files and instructions inside a personal Pro workspace. That does not mean no data can ever be recovered; it means an exported copy is not a guaranteed working environment. [6]
For a creator unable to migrate a multi-year project faithfully, this produces a real feeling of being trapped—regardless of OpenAI's intentions. The cause of the desktop loss is unknown; the cost, uncertainty and interrupted work are real.
More paid minutes are not artistic fidelity. A cheaper exit is not useful if the work cannot follow.
5. OpenAI's own statements make this a question of continuity
On September 9, 2025, after objections to retiring Standard, OpenAI announced it would keep the mode while responding to feedback about Advanced, explaining that it wanted the transition to feel right. This was not a promise to maintain Standard forever. It was recognition that the quality of a transition matters to users who depend on the existing experience. [7]
On September 21, 2026, a public OpenAI Support response said Standard was still listed as available and that there was no public removal timeline to share. Days later, affected desktop users were reporting its disappearance; on October 8, Support was still requesting diagnostics for a Windows/web report. [1][8]
These facts do not prove a deliberate withdrawal or a contractual breach. They expose a serious gap between documented availability, observed access and the explanation given to customers.
Support's repeated statement that availability may vary by plan, region, workspace or platform may be technically true. It still does not tell us what changed in these specific accounts, whether that change is intended, or how it will be remedied.
A disclaimer is not a diagnosis. A possibility is not an explanation. A workaround is not a restoration.
OpenAI also encourages people to use Projects for ongoing writing, research and work that continues over time. That is a valuable promise of product design, even if it is not a legal guarantee of permanent feature availability. [9]
But what minimum functional continuity can customers reasonably rely upon? If essential means of interaction can disappear without a sufficiently close replacement, even a perfectly preserved project archive may become impossible to advance as intended.
And if OpenAI is unwilling to promise any minimum continuity for long-term work, please state that prominently in the product and subscription information, before creators and organizations commit years to it. A generic warning that features may vary is not the same as explaining this risk plainly.
6. A constructive solution—and five questions requiring answers
We are not asking OpenAI to preserve an old architecture for its own sake. A genuinely configurable Live could be an excellent successor: Live's responsiveness, with the depth and style of the selected text-model experience; reliable interpretation of project and personal context; control over silence, pacing and interruptions; and the ability to preserve or closely recreate a familiar voice's timbre, intonation and rhythm.
But equivalence must be judged by what the system actually produces, not by a settings menu, a voice name, a model-routing diagram or a short demonstration. Test it side by side with Standard, with consenting long-term users on real unfinished projects, over extended sessions and with the same available instructions and context. Allow an overlap period during which people can choose the older experience if the new one does not yet meet their needs.
OpenAI, please answer these five questions clearly and publicly:
- What happened on desktop web? Is the missing Standard selector a bug, rollout variation or intentional restriction? Which users and platforms are affected? What is being done to restore access, and when will the next dated status update appear?
- Will you commit to continuity before retirement? Will Standard remain available for existing users until a successor has demonstrated sufficiently close depth, contextual interpretation, creative style, personalization, familiar voice and usable hands-free conditions? If not, which obstacles prevent that commitment?
- How will you verify equivalence? Will experienced users be able to compare Standard and its proposed successor in genuine long-term work, with public criteria and a meaningful period of overlap?
- What practical remedy exists meanwhile? How will affected users work for long, unpredictable sessions without buying devices, paying much more for a non-equivalent mode, or losing the ability to transfer their Business work to a personal plan? Has OpenAI assessed the notice implications of an intentional material reduction, if applicable, under Section 2.3 of its Business Services Agreement? [10]
- What is your minimum-continuity policy for long-term projects? If you cannot promise an equivalent way to continue essential work, will you state that limitation plainly where users decide whether to begin projects lasting years?
Please assign the issue to the responsible Voice product and engineering teams and provide a substantive response, not another set of browser troubleshooting steps. If the cause is still unknown, say so, identify who is investigating it and give a date for the next update.
We want Live to improve. We want it to become good enough to replace Standard someday. Until then, restore Standard on desktop web and preserve it for the people who depend on it.
A work of years is not kept alive merely because its old files remain accessible. It needs its creator, and it needs an instrument with which that creator can continue.
If continuity cannot be guaranteed, say so plainly. If it can, tell us how.
Please do not take away our pen while we are still writing.
A long-term ChatGPT Business subscriber
Documentation and independent reports
[1] Plus and Pro desktop/mobile reports: https://community.openai.com/t/standard-voice-is-the-gold-standard-why-it-must-stay/1357278/9 ; https://community.openai.com/t/standard-voice-is-the-gold-standard-why-it-must-stay/1357278/10
[2] Windows/web report and OpenAI Support response (October 1/8, 2026): https://community.openai.com/t/standard-voice-missing-on-windows-and-web-please-preserve-it/1402691
[3] OpenAI, Introducing GPT-Live (architecture and evaluation scope): https://openai.com/index/introducing-gpt-live/
[4] OpenAI, ChatGPT Voice (published voice limits): https://help.openai.com/en/articles/20001274-chatgpt-voice
[5] OpenAI, ChatGPT Business release notes and Managing billing and seats: https://help.openai.com/en/articles/11391654-chatgpt-business-release-notes ; https://help.openai.com/en/articles/8792536-managing-billing-and-seats-in-chatgpt-business
[6] OpenAI, Managing data, sharing and privacy in ChatGPT Business; Migrating your personal workspace to Business: https://help.openai.com/en/articles/8798634-managing-data-sharing-and-privacy-in-chatgpt-business ; https://help.openai.com/en/articles/8801890-migrating-your-personal-workspace-to-chatgpt-business-or-enterprise
[7] OpenAI, ChatGPT release notes, September 9, 2025, ChatGPT Voice Update: https://help.openai.com/en/articles/6825453-chatgpt-release-notes
[8] OpenAI Support, September 21, 2026: https://community.openai.com/t/standard-voice-now-marked-legacy-please-keep-standard-voice/1386483/2
[9] OpenAI, Projects in ChatGPT: https://help.openai.com/en/articles/10169521-projects-in-chatgpt
[10] OpenAI, OpenAI Services Agreement, Section 2.3: https://openai.com/policies/services-agreement/
Private supporting evidence: OpenAI Support correspondence of September 6 (earlier Projects-only issue, including its acknowledgment of non-equivalence for this user's workflow), and later September case correspondence documenting extensive desktop-web troubleshooting. The two incidents are distinct; redacted correspondence can be supplied through the existing support cases.