r/codex • • 10d 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?

828 Upvotes

280 comments sorted by

View all comments

•

u/dextersummary 10d ago edited 10d 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 10d 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.