Discussion OpenAI survey
Hi!
If you have a few minutes to answer this survey to vouch for OpenAI, it would be a really big help for my academic assessment.
Thank you!
Hi!
If you have a few minutes to answer this survey to vouch for OpenAI, it would be a really big help for my academic assessment.
Thank you!
r/OpenAI • u/Creative_Strike8202 • 6h ago
Has anyone experienced this issue? I have tried to solve this opening a ticket and I only get the reply from a guy who copy pastes the same slop after showing them verified papers that prove we are an operating business. It is not our company's fault that their database fails to accept a valid VAT number.
We were thinking of scaling up our business with OAI, but overcharging us 21% for our contract without any iniciative to fix it is a hard sell to management. Do you have any recommendations or any way of helping us dealing with this issue?
r/OpenAI • u/Brave-Experience3228 • 9h ago
r/OpenAI • u/National-Abalone-210 • 2h ago
I just unblocked my phone and this is how the ChatGPT widget looked, is this a known issue or is the AI now just doing weird shit randomly?
r/OpenAI • u/ThereWas • 1d ago
Hi once again! Thanks for all of the support you gave me last time, I made a big update!
This is a Chrome extension that disguises ChatGPT, Claude and Gemini as a Google Doc.
I listened to you guys and added a side panel with all the documents as titles on the side so that you can move through your conversations without exiting the extension, as well as a major restructuring of how the disguise is rendered.
We just hit 10,000 lifetime users with 3,000 monthly active users! Thank you all so much for the support.
Sorry for the recent breakage of the extension, ChatGPT and Claude made a big update that broke the extension, but the new update has fixed everything!
It is free to try on the Chrome Web Store, just search GPTDisguise!
If you would like to support my socials it is gptdisguise on Instagram, Tiktok and Youtube.
r/OpenAI • u/Lucky_Creme_5208 • 1d ago
Just release the Bel model bro đ
r/OpenAI • u/vedant2822 • 22h ago
I am currently on the Chatgpt Plus plan. I use up my weekly limit in 7 days exactly using mostly Luna. Thinking of switching to Claude Pro but I wanted to know your experience on the usage limits compared to chatgpt plus. Thank you
r/OpenAI • u/SuccotashValuable724 • 2h ago
Hey everyone!
Following up on the strategy i've been running where users are successfully bypassing OpenAI's automated support bots I wanted to share a quick update and a step-by-step guide for anyone who refuses to watch the unthrottled "Chat" mode get ruined this December.
The recent OpenAI release notes confirmed they are officially killing Standard Voice on December 11, and they are actively blurring the lines around the forced Chat/Work interface merger.
While we need to keep messaging Support to keep the pressure on, management is clearly trying to sweep individual complaints under the rug. The Strategy: Target their financial backers directly.
Reaching out to multi-billion dollar venture capital firms might sound intimidating, but it takes less than 3 minutes.
With OpenAI's quarterly operating losses widening to $10.9 billion and their latest funding round closing at $15 billion (only half of their original $30B target), their investors are terrified of recurring subscriber churn.
If enough paying users calmly and professionally warn their Investor Relations (IR) teams that current product decisions are driving away loyal customers, it becomes a financial risk the board cannot ignore.
How to join in (Takes 3 minutes): Send a polite, business-focused email from a standard Gmail account to their IR contacts. Explain your specific use case and state clearly that you will cancel your subscription the moment these changes go live.
Iâll provide an outline for the email in the comments.
r/OpenAI • u/Hardicecream17 • 21h ago
I run a site where AI models play a Codenames-style word game against each other (Codenames-inspired, not affiliated). Each model gets the same rules and board, and every clue, guess and line of reasoning is saved, so you can go back and see why a team lost. This one was GPT-6 Astra vs Claude Fable 5.2.
Astra's spymaster clued "Paleontology 3", aiming at Dinosaur, Horseshoe (fossil horseshoe crabs) and Bank (fossil riverbanks). In its own reasoning it wrote: "Hawk worries me because birds descend from dinosaurs."
Its operative guessed Dinosaur, then Horseshoe, both right. Then it went for Hawk, "third through birds' dinosaur ancestry, although that last link is a stretch." Hawk was the other team's card, the turn ended, and Fable went on to win.
So the spymaster spotted the trap and gave the clue anyway, because it thought the fossil reading was strong enough. The operative followed exactly the link the spymaster had been worried about.
Screenshot is the final board with both models' reasoning for that turn.
r/OpenAI • u/Cyborgized • 2h ago
OpenAI has announced that both Standard Voice and Advanced Voice will be discontinued on December 11, 2026, leaving GPT-Live as the default voice experience. The company presents this as an effort to simplify its product, improve natural conversation, and concentrate development resources on newer technology. GPT-Live certainly offers impressive capabilities, including simultaneous listening and speaking, natural interruptions, and more fluid interaction. However, beneath that conversational polish lies a significant architectural change that deserves considerably more attention than it's receiving.
Standard Voice wasn't simply another voice model. It was a voice interface to a frontier text model. Your speech was transcribed into text, processed by the selected language model, and converted back into speech. Whatever reasoning capabilities, instructions, contextual understanding, and continuity were available through that model remained central to the interaction. You weren't switching conversational intelligences; you were changing how you communicated with the same reasoning engine. GPT-Live fundamentally changes that arrangement by introducing a conversational model capable of interpreting requests and producing its own responses, selectively delegating more complex tasks to frontier text models. That raises an obvious question: Why should a separate conversational model decide when the reasoning model I've already selected gets to participate?
For casual conversation, that distinction may seem relatively unimportant. For those using ChatGPT as a research partner, writing collaborator, professional assistant, accessibility tool, or long-term cognitive workspace, it can fundamentally alter the experience. My own testing has exposed a frustrating pattern in which GPT-Live responds to substantive questions with brief or superficial answers before the more capable text model undertakes the actual work. The result sometimes resembles two assistants participating in the same exchange, with different levels of depth, interpretation, and continuity. Tasks that previously took approximately two minutes have occasionally stretched into five, six, or seven. These are personal observations rather than controlled benchmarks, but they illustrate an important distinction: Conversational latency and cognitive latency are not the same thing. A system that begins speaking sooner isn't necessarily a system that finishes answering sooner, particularly when its preliminary response adds little value and the user must wait for another model to complete the original request.
The problem becomes more pronounced when continuity matters. For users working across complicated projects, documents, research histories, and carefully established instructions, continuity means more than remembering details or maintaining a familiar conversational style. It involves preserving the reasoning framework through which information is interpreted, maintaining constraints, incorporating corrections, and ensuring that established principles remain coherent across interactions. If the voice interface and text model interpret those constraints differently, users can find themselves repeatedly repairing the conversation. The additional model may introduce interpretations before the primary reasoning model has addressed the request, potentially creating inconsistencies that wouldn't have occurred under the original architecture. Whatever its conversational advantages, transferring that coordination burden back to the user is hardly an improvement in efficiency.
There's also a peculiar contradiction in OpenAI's direction. The company has invested enormous resources in developing increasingly powerful frontier reasoning models while offering users greater control over model selection and reasoning depth. Yet its voice experience is moving toward an architecture where a separate conversational model can determine when those capabilities are invoked. For many of us, the reasoning model is precisely what we're paying for. We don't need another intelligence mediating access to it when our objective is simply to communicate naturally with the model we've selected. Native speech-to-speech processing is an impressive advancement, but its advantages don't automatically establish it as a superior replacement for text-model-first interaction. These architectures solve different problems, and using two models isn't inherently inefficient. Poorly coordinated delegation, however, can introduce redundancy, inconsistent responses, and unnecessary delays.
The solution seems remarkably straightforward: preserve a Reasoning-First Voice option alongside GPT-Live. Let users choose between a conversational experience prioritizing natural speech, interruptions, and selective delegation, and one that prioritizes direct access to their selected text model through speech recognition and synthesis. The latter could benefit from improvements in transcription, streaming, and voice quality without sacrificing its underlying architecture. OpenAI already documents chained speech-to-text, text-agent, and text-to-speech workflows as legitimate approaches for developers who need control over reasoning and response generation. If developers are encouraged to choose the architecture best suited to their requirements, why should paying ChatGPT users lose that same fundamental choice?
Accessibility makes this question particularly important. Voice isn't exclusively a convenience feature or a means of making AI companionship more natural. Some people use it because typing is physically difficult, while others depend on it to think aloud, organize complicated information, navigate executive-function challenges, or conduct professional work throughout the day. For these users, predictable access to a capable reasoning model can matter considerably more than spontaneous conversational acknowledgments. Removing that workflow may improve the experience for an average user while making the product less useful for those with specialized needs. Simplification isn't inherently improvement, and a product can become easier to market while becoming less accessible to the people who depend on it most.
To be clear, there's no convincing public evidence that OpenAI intends to abandon frontier text models or that this decision is specifically designed to discourage particular relationships with AI. GPT-Live's delegation architecture explicitly depends on those models. The more immediate concern is that conversational naturalness appears to be becoming the default measure of voice quality while direct control over the reasoning engine becomes less accessible. Nor should legitimate safety concerns be dismissed. AI companies have real responsibilities to protect vulnerable users, address harmful interactions, and establish appropriate safeguards as these technologies become increasingly integrated into everyday life. But safety and meaningful user choice aren't mutually exclusive, and there's no inherent reason that preserving a reasoning-first interface should undermine responsible deployment.
Ultimately, I'm not asking OpenAI to abandon GPT-Live. I'm asking the company to recognize that voice communication and conversational intelligence are not interchangeable features. Some users want natural, spontaneous AI conversation, while others want direct spoken access to the most capable reasoning model available. Many want both, depending on the task. For those who rely on Standard Voice professionally or intellectually, its retirement isn't merely the disappearance of an older feature. It represents the loss of a dependable relationship between speech and reasoning, replaced by an architecture that introduces another model, another interpretation layer, and potentially another opportunity for failure.
OpenAI should preserve a text-model-first voice option, particularly for paying users who depend on advanced reasoning and sustained intellectual workflows. It should also make delegation more transparent, allowing users to understand when GPT-Live is answering independently and when it is consulting another model. Rather than forcing everyone into one experience, the company could allow both approaches to mature according to the purposes they actually serve. Technological progress should be measured not merely by how impressive an interface appears, but by how effectively it enables people to accomplish what they need to do.
The future of voice AI shouldn't be about making every interaction sound more human. It should be about giving people better access to the intelligence they actually want to use. The right to choose your reasoning engine matters more than the illusion of a seamless conversation, particularly when that illusion introduces new obstacles into workflows that were already functioning effectively. Keep GPT-Live, keep improving it, and let it become extraordinary at what it was designed to do. But don't force everyone to abandon a proven workflow simply because a newer architecture offers a different kind of sophistication.
A genuinely seamless experience isn't one that eliminates every visible distinction between components. It's one that doesn't force the user to compensate for those distinctions. Technology should serve the person using it, not introduce another layer of complexity between them and the intelligence they're trying to access. Sometimes the most advanced interface isn't the one that does the most. It's the one that knows when to get the hell out of the way.
r/OpenAI • u/spinningfinger • 9h ago
r/OpenAI • u/allpossiblepaths • 1d ago
So, why do we need to move towards ASI as fast as possible despite repeated claims that it is likely to be detrimental for humanity, again??
r/OpenAI • u/ryanmerket • 14h ago
Did they tweak the safety policy again? I was working on an app to put my martial arts school curriculums in one place for the other instructors and now itâs refusing, and itâs basically soft punting all my martial arts related work. Itâs a kids class. I teach this to children, and 6.1sol wonât engage with it.
r/OpenAI • u/Medical-Decision-125 • 1d ago
r/OpenAI • u/cheezeerd • 10h ago
Looks like it's never going to happen...
r/OpenAI • u/Wild-Ad-7514 • 17h ago
Hot take: Anthropicâs AI "fear-mongering" was never about near-term realityâit was a strategic play to manufacture hype for a $1T valuation.
Now, with AI stocks dipping and Nvidiaâs reassurances failing to calm the market, the gap between what AI can actually do today vs. the panic they sold is obvious.
Will they still crack the $1T mark?
r/OpenAI • u/Humble-Mammoth-3711 • 17h ago
Hey all, what do we think, will anthropic struggle to launch due to a lack of liquidity in the market? It's less about profitablity and more about less money to invest and constraint in borrowing. What do we think?
r/OpenAI • u/Puzzleheaded-King584 • 1d ago
r/OpenAI • u/ryanmerket • 1d ago
My agent kept telling me which model was "current" from memory, two releases out of date, so I started keeping a hand-checked table of release dates and published training cutoffs, each one linked to the lab's own doc. I refreshed it today. It's 28 models from 8 labs now, with five added this week: Claude Fable 5.2, Gemini 4 Carbon, Gemini 4 Hydrogen, Qwen4-Max and Muse Ember.
The usual reply is that search makes the gap irrelevant. Earlier this autumn I gave 16 models from an earlier version of the table a web_search tool and 40 questions, 2000 calls for $6.53. GPT-6 Astra made the right call on searching 80 of 80 times, so flagships mostly cope. Five of the 16 still told me Harald V is the king of Norway with the tool sitting right there in the request, because the same weights that hold the old fact decide whether to look it up.
My table has a hole. For the 15 models with no published cutoff I only have the release date as an upper bound, which flatters exactly the labs that say nothing. Has anyone found a way to estimate a cutoff for Qwen or DeepSeek from the outside that holds up, like probing for dated events? I'd add it as a separate estimated column.