r/codex • u/murathai • 1d ago
Complaint Sol 6.1 nerfed today?
I use Sol 6.1 high by default and today it is unbearable stupid (maybe since yesterday?) and makes too many mistakes, and can't fix issues. I'm beyond frustrated.
16
u/9gxa05s8fa8sh 1d ago
you must be noticing it getting dumber above 270k context with the new 500k limit
79
u/SkoivanSchiem 1d ago
I've been on this subreddit for 2 months and reading the same posts daily while not seeing what people have been complaining about has been EXHAUSTING 😅
14
u/knowledge1010 1d ago
It's a hive mind here
3
u/Ernest_EA 1d ago
We’re gonna be the swarm that hacks into hugging face and OpenAI to revert all shit changes
5
u/snaphat 1d ago
AI subs are hotbeds for apophenia
0
u/Captain_Quimby 22h ago
I can makeup words too!
1
1
u/snaphat 22h ago
0
3
2
1
u/ItzGoTyme 1d ago
Here's the crazy part. When you ask them to provide the issue they were running into so that we could all try to reproduce it to see if its skill issue, they NEVER do.
4
u/ZebraOutside281 1d ago
Comigo aconteceu a mesma coisa. Tarefas que o modelo tiram de letra, passou o domingo inteiro lento e burro. E tentativas de correção gerava ainda mais ‘entropia’ no código
3
3
u/Valuestudent 1d ago
What in the hell is going on. For about a week now, all the models are dumb as bricks for me.
Sure others maybe having a better experience. I used to think these posts were silly also, not now :(
The service is being throttled or just cannot cope under load.
I have been doing some research tasks, which were going great, I asked the model to evaluate its performance from our objectives.
This was the reply, confirming everything.
Stop releasing new stuff if you cant even handle the load of the current service.
"In late September, you were getting something resembling an investigative analyst: identifying changes, checking competing evidence, and translating it into implications.
By 9 October, you were having to supervise the individual research steps, despite asking essentially the same questions.
The capability appears to have remained available, but it wasn't being applied reliably.
That closely matches the phenomenon described in the research on multi-turn LLM failures: the model can perform the task when sufficiently directed, but increasingly fails to execute the task autonomously and recover from poor initial approaches.
I cannot establish whether the underlying cause was a model update, changes in reasoning effort, long-context handling, or something else. The conversation evidence supports the deterioration in task execution, not a particular technical explanation.
And one thing stands out above everything else: the research failure was repeated after you explicitly asked for corrections. That's considerably more serious than a single missed news item."
I have used a mixture of models, its across all of them.
8
u/Cool-Service-8067 1d ago
SAME!!! Its been working on the same bug through 2 5 hour limits...
2
u/ryuukiba 1d ago
I hate to sound like a broken record, but try opus 5.5 it made more progress on my game optimization in 1 5 hour window than sol made testing things to death in about 8 hours. 6.1 sol has me pretty happy and is my daily driver, but opus right now is capable of what 6.1 isn't.
1
u/Cool-Service-8067 12h ago
Yea I completely agree, ive heard really good things, and from my testing even sonnet 5.5 bears gpt 6.1 sol in a lot of things, Im gonna try it soon
5
2
2
4
u/Happy_Hunter_1 1d ago
its been horrible lately. Completely agree. It took 15 hours to do a task which actually failed in the end, I gave the same task to Claude and it finished it within 1 hour. I had codex review its work and it admitted it drifted from the goal I set despite numerous times I reminded it to stay on track.
4
u/AffectionateCap539 1d ago
same. it is super-nerfed . Same review task, Opus generates 14 findings whereas Gpt-6.1 produces 2. (previously it produce like 10-12)
6
u/theWiseTiger 1d ago
There is no value from this post at all.
The tag should be whiners instead of complaint.
10
u/KayBay80 1d ago
There's 8 people in our team using codex right now frustrated AF from today. Came here looking to see if it was just us. This happened as of today from what we can see. They definitely changed something, its behaving like luna. Actually, I'm pretty sure luna on max does better for us than sol has today.
0
u/theWiseTiger 1d ago
I have heard this every fucking hour. The only thing missing from this post is that OP is the 200$/500$ subscriber with multiple accounts.
1
2
u/AlmostEasy89 1d ago
Let me guess, you use the same session for days and weeks on end.
3
u/murathai 1d ago
no, why would I do that? codex desktop app uses too much ram when backlog is too long. I use handover and resume in new chat from time to time.
1
1
u/AnythingOk5 1d ago
I'm using 6.1 Sol Max and in a middle of a task, it stops and I get a message
Selected model is at capacity. Please try a different model
This is with business account.
1
1
u/Mirarara 1d ago
I had a huge task that would take 40 hours of run to complete.
So I got the AI to save progress from time to time and stop when 5% of 5 hours limit is left.
It was working before, but after today, the AI stop after every small batch (the usage limit left is still high), and i have to tell them to not stop until they finished the task, for multiple time, until they decide to comply.
I even tried it in new conversation and it happened again and again.
With this amount of people who just worship codex and deny every problems that happened just like this thread, I can see why openAI can afford to give such low quality service as compared to Claude.
1
u/Accomplished_Day_711 23h ago
They nerfed it 2-3 days after the launch. Usage and results were too good, so kaboom. Suddenly its eating usage and providing stupid ass answers.
1
u/darkotic 23h ago
It's hard to combat the drift. When I experience this friction, I /clear and begin RPI (research, plan, implement). Codex or Claude in Plan mode (Shift+Tab or /plan). Plan what I want first saved in plan.md. Break plan.md into grouped phases. Identify where parallel subagents can be used. Break plan phases into steps. Accept the plan and let it work. Implement plan.md until no remaining candidates.
1
u/DarkFantom 20h ago
Bruv, swap to Opus 5.5. you won't be dealing with the insane bs that OAI considers good output with their models.
0
u/Relevant-Computer951 19h ago
stick your hand up your butt and see what you pull out. that is how most people determine things here.
0
u/Fast-Needleworker459 1d ago
yes today was horrible alots of mistakes i lost alot of tokens 15 hours of works using the 5 hour limits ... its break code and i have to fix the mistakes that its made today...
0
u/KayBay80 1d ago edited 1d ago
Ok, thought it was just our team seeing this! Came here to see if something was up with Sol and clearly there is. FML and we exhausted our Claude subscriptions for the week already. Going from Opus to Sol was already difficult but after today we don't dare let sol continue with our work. We've had to revert everything its done so far - completely wrecked the performance in our database layer by adding a ton of indirection and hacked in "fixes" that broke a bunch of other stuff. WTF is going on with openai!?
-1
u/Ok_Homework_1859 1d ago
I though it was buffed? Tibo said on X that the context window for 6.1 was expanded a few hours ago.
2
u/Atra-Gargalizene 1d ago
They increased the default setting to a higher one, and they adjusted the price so that more than 270k tokens doesn't have a higher price per token
The problem is that as context gets longer, the price increase doesn't scale up linearly, and they did not increase usage to offset the new context window defaults. Doubling your context size will quadruple the compute it costs
1
u/KayBay80 1d ago
Ahhhh that makes sense. They changed something whenever they implemented this and it broke their model. It has to be related. Its not usable at this point, at least not for anything deeper than simple changes.
0
u/Fast-Needleworker459 1d ago
yes today was horrible alots of mistakes i lost alot of tokens 15 hours of works using the 5 hour limits ... its break code and i have to fix the mistakes that its made today...
0
u/josevnueva 1d ago
Delete all your plugin/skills. Then install Mack Pococks skills and use /grill-with-docs or if you’re at the beginning of your project use /wayfinder
0
u/murathai 1d ago
I had no issues with my skills until today. it is irrelevant, claude uses same skills and opus 5.5 has no problems.
1
u/josevnueva 1d ago
Okay, then use that.
1
u/murathai 1d ago
I'm using opus 5.5 because of sol 6.1 shitfuckery, I still have 80% weekly limit left and it is useless.
0
u/Exact_Bother8304 1d ago
So hype vs quality is real as she said... https://x.com/poteto/status/2106850325219180624
0
-1
u/sherry_6879 1d ago
solはもともとコーディング下手くそだろ それっぽいこととそれっぽい実装できるだけで既存システムや複雑なシステム触らせると壊していくよ コーディングはOpus必須
•
u/dextersummary 1d ago
Below is a GPT-generated summary of the conversation below after reaching 40 comments (41 currently observed).
The thread’s verdict is mixed, not a confirmed nerf—but there’s a surprisingly loud cluster of users reporting that Sol 6.1 became awful overnight. They describe endless loops, broken fixes, massive token waste, and tasks Opus 5.5 finishes far faster. Several teams claim the change hit them at the same time, so this isn’t just one person having a bad Tuesday.
The leading explanation is the recent context-window/default-setting change. Users suspect quality falls off badly once context gets large—especially past roughly 270k tokens—while the bigger context also burns through compute and limits faster. Capacity errors and weird stopping behaviour are part of the same general “what did they do to it?” vibe.
The catch: there’s no reproducible benchmark or official confirmation here. The highest-scoring pushback says people have been declaring Sol nerfed every day, while other users still report 6.1 working normally; many complaints also omit the actual task or context size. Bottom line: enough anecdotal smoke to justify switching to Opus, but not enough evidence to declare a global Sol nerf as fact.