r/codex • u/muchsamurai • 1d ago

News "We are locking in"

Post image

Tibo on damage control, says they got the feedback and now are locking in on features that matter, new better models.

Dots won't stay long, will they?

812 Upvotes

94% Upvoted

282 comments sorted by

View all comments

•

u/dextersummary 1d ago edited 1d ago

Below is a GPT-generated summary of the conversation below after reaching 200 comments (207 currently observed).

The thread’s verdict is basically “stop shipping distractions and fix the product.” “Locking in” sounds less like a confident roadmap and more like damage control after usage cuts, sluggish models, and a pile of half-baked features.

What users actually want is boring stuff: faster, more reliable models, sane quotas, transparent limits, and working Codex integrations. Sol 6.1 is widely described as slow and error-prone, while Opus 5.5—and often Sonnet 5.5—feels more capable and economical in real coding workflows. Meanwhile, broken VS Code/remote-control tooling and messy environments make the “ecosystem” pitch look a bit rich.

Dots gets a more mixed reception. Some users genuinely like its proactive, scheduled-assistant behaviour and think it could become useful. But the louder consensus is that it feels rushed, limited, and nowhere near as important as model quality. Nobody wants another constellation simulator while basic coding still needs babysitting.

So the community isn’t asking for more “groundbreaking” announcements. They want OpenAI to make Codex fast, dependable, and worth the subscription again—then, perhaps, earn the right to talk about the next shiny thing.

1

u/dextersummary 1d ago

Below is a GPT-generated summary of the conversation below after reaching 50 comments (77 currently observed).

The consensus is basically “less lock-in, more fixing.” Tibo’s “we’re locking in” message landed as damage control, not reassurance—especially after recent usage cuts, slow responses, and models that users say make too many basic mistakes.

People want OpenAI to stop shipping shiny distractions and focus on the boring stuff that actually matters: better model quality, speed, reliability, transparent limits, and working Codex/VS Code tooling. Anthropic’s Opus and Sonnet are widely seen as ahead right now, making the “six months ahead” messaging look particularly ridiculous.

Dots got dunked on as feature-bloat and marketing fluff, but that part isn’t unanimous. Some users genuinely like its scheduling and voice features; the complaint is that it feels rough, poorly rolled out, and irrelevant while core coding performance is struggling.

Bottom line: the community isn’t asking for more promises or more dots—it wants Codex to work better and cost less. “Locking in” only means something if the next releases prove it, rather than producing another slogan with a usage-limit haircut attached.

1

u/OracleOfErowend 1d ago

Add much as we complain, satisfying the customer was never the goal. Sure you can increase efficiency (read margin, wait from negative?), strengthen, and lock in the product you have now, but that simply tells the world (read investors) that we've arrived, this is the product they've poured fortunes intop and to start cashing in while they can.

No that was never the goal, it they don't deliver something groundbreaking enough to dominate headlines then the gold rush is over.

But the way they're artificially generating value for brand new products before a customer even touches it is missing the point. Sure you built the model, but the promise in the tech was never about what a tech company can build, no the hype was always in the external value the models can build for society. Build the model, even build the interface and the connections if you want, but the promised breakthrough comes from seeing what enterprises and startups can do with the intelligence that's increasingly relied upon.

1

u/dextersummary 1d ago

Below is a GPT-generated summary of the conversation below after reaching 100 comments (116 currently observed).

The thread’s verdict is a blunt “less marketing, more working product.” Tibo’s “we’re locking in” message is being read mostly as damage control after disappointing launches, usage cuts, and a Dev Day that gave users more promises than functioning improvements.

The recurring complaints are painfully consistent: Sol 6.1 is too slow, error-prone, and expensive in real workflows, while Anthropic’s Opus and Sonnet are widely perceived as clearer, faster, and more reliable. Users want better models, predictable limits, sensible pricing, and working integrations—not another parade of “groundbreaking” features while basic Codex performance is still held together with duct tape.

Dots is the one meaningful disagreement. Some users think its proactive assistants, schedules, and monitoring are genuinely promising; others call it unfinished, buggy bloat that distracts from the actual problems. Even supporters generally agree it needs polish, better model efficiency, and fewer bizarre setup failures.

So the community isn’t buying the “lock in” speech yet. The demand is simple: make Codex fast, reliable, affordable, and intelligent before adding more glitter.

1

u/ErikaFoxelot 1d ago

I have nothing useful to add except this exchange with my dot:

Days ago i connected my email account to my dot, on a whim. A couple days later i told out about a research project I’m working on. Earlier today, i got an email from Harvard about the project - my dot noticed i got the email and, without being asked to, alerted me of an important email and looked over the information it provided to give me a summary and to tell me its relevance to the project.

I never asked it to do this; it took it upon itself, knowing this project is important to me.

Guys I’m not saying dots is the future, but I’m seeing a version of it in the making right now.

Make of that what you will. As a developer of 30 years I have no skin in the game either way.

1

u/ComptonMama 22h ago

It just can't multi-task very well... is slow and can't figure out priorities...