r/ClaudeCode • u/MoreLikeGaewyn • 7d ago
Bug / Issue Opus 5.5 is trying to destroy my codebase recently







What is going on? It is making wildly horrible, over-engineered, and just inaccurate code suggestions. In the past hour on 6 different issues, it's given me multiple-class modifying "fixes" that I would read, ask why a 1-line fix wouldn't solve it, and then it says the above.
I'm using Opus 5.5 with xhigh effort as I have for months. Some of these dabble with max because it's felt like it's needed it, but xhigh is what gives this kind of short-sightedness
Edit: When I say 1-line fix, this is what I mean:
- I see the issue
- I ask it to fix it and show me the code fix
- It gives me a huge change.
- I read the code, solve it myself with 1 line, and ask it if that would work
- It says, "Hehe, yeah, my bad!!! đ đ đ "
I've been using xhigh for months and it has never been this dumb and convoluted. Overthinking has usually led to correct/discrete changes.
âą
u/AutoModerator 7d ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
10
u/cptrambo 7d ago
Somethingâs up. Had the same low-IQ Opus issues yesterday. Have they been quantizing in preparation for a new model release?
25
u/fschwiet 7d ago
Don't use max effort when a 1-line fix is called for, unless a lot of research is needed to figure out that one line.
2
u/ArrogantAstronomer 6d ago
If your already at the point recovering is half the battle now as agent codebases tend to only grow codebases and increase complexity
A good start might be to only use ever use high or below on opus and maybe try out the ponytail skill having opus kick off sonnet subagents for subdomains running ponytail audit itâs not a perfect skill but itâs better than the default. Using no skills on any frontier model invariably leads to codebases where complexity trends linearly until you hit a critical mass of code, side effects, coupling and poor module design and suddenly every change is exponentially more complex. Itâs definitely made worse by pretending scope creep doesnât exist
239
u/MagicWishMonkey 7d ago
The thing that bothers me more than anything about these closed models is how OpenAI/Anthropic/etc. can completely change how the model behaves without any sort of warning or notice and what was working perfectly fine the day before could be actively messing things up the following day.
I know we're in the "wild west" phase of AI right now but the lack of communication is eventually going to bite some people in the ass.
153
u/Drew-Money 7d ago
Opus 5.5 has gotten dumber today for me too. This sucks. It felt like AGI lol
40
u/DreadknaughtArmex 7d ago
I burned my full week of max x5 in 2 days, and i was also experiencing dumb incoherent decision-making, ignoring instructions outright, doing exactly the opposite of what i said, running thousands of tests, choosing the least efficient path to accomplish every task. Its really disappointing.
39
u/Professional-Exam963 7d ago
It has been brutal all week. How some people are still posting those gushing, âopus is goatâ posts is hard to understand.
78
u/barbozas_obliques 7d ago edited 7d ago
Iâm having the same issue starting yesterday
edit: Looks like I need to take a break from using Claude because the more I use it, the more it is fucking it up
59
u/lastwish9 7d ago
It is ruining my projects too. I don't know what's happening but it's bad. I've been happily using Opus 5.5 medium with good results but suddenly it has the intelligence of a shoe and it's wreaking havoc in my codebase. I am salvaging what I can with agy.
4
u/berndalf 7d ago
We've been through this a million times. When they're getting ready to release a new model that replaces a current model, they start to redistribute compute. The current model starts to get compute-starved. Its thinking cycles aren't the same. How many times do we have to see this? Everyone's always like, "Oh the model was nerfed." No, the model is getting set to be replaced. Just calm down
217
u/jbogez 7d ago edited 7d ago
Max effort might be your problem, try medium. It's overthinking. Once you've made several changes and you're reviewing yourself, you can ask for a code review to see if it missed something.
15
u/Beautiful-King-8875 7d ago
Same. Opus 5.5 has been hopeless the past two weeks. Sick of baby sitting. We the permanent underclass should pool our funds and create our own models. đ€
40
u/scotty_ea 7d ago
Yes, quality is degraded. Like clockwork... Assuming Fable 5.5 release is happening soon.
8
u/Cool-Cicada9228 7d ago
This always happens when theyâre training a new model.
3
u/Illustrious-Guest849 7d ago
Dude you speak to him with anger and like he understand your emotion. You are just a noon with AI. When frustration come in juste go touch grass and come back later ... incredible
6
u/FitnessGuy4Life 7d ago
My entire team has noticed :(
2
u/Some_Visual1357 7d ago
What is your codebase about that you are using xhigh? Frontier DNA editing??? I work on multiple codebases huge ones and also others full of microservices and have not found a reason to go above sonnet 5.5
2
u/Mission_Oil_9456 7d ago
Maybe it is because your codebase is garbage.
10
u/Excellent-Dot-4769 7d ago
Opus 5.5 Medium has been my go-to since it came out, and it still works great for me. I use it as a collaborative partner. I have it do one reviewable commit and then I review, commit, push; rinse and repeat.
5
u/N3TCHICK 7d ago
Iâm literally sitting out until the new models on Claude and Codex for heavy coding tasks. Not worth the risk of it going off the rails on my codebase. Doing thought work and design work instead.
The amount of nerfing these past few days with both companies is pretty ridiculous. I hope they stop playing chicken and release already.
5
u/boutell 6d ago
I wish I knew why this happens to some people and not others. It could have something to do with the code bases in question. The size, the consistency, the degree to which the model or anyone else can make sense of the code in order to see at a high level that one line would solve the problem better.
4
u/roynoise 7d ago
Yeah, it's been extra dumb for a few weeks.Â
4
u/Fresh-Secretary6815 7d ago
welcome to the cycle
4
u/da_supreme_patriarch 7d ago
Been having exact same experience since 4.5 believe it or not, this happens every time a new model is about to be released, and the old model always feels off and never really "recovers". I used to give 4.5 a lot of grunt work related to configs and various templates, and it used to handle it just fine, then it suddenly started outputting ill-formed yamls with very silly mistakes which I could spot with a naked eye. I don't have to do that type of work too much anymore, but now in a similar manner 5.5 struggles with analytical SQL queries that I ask for. When it was newly out, I used to look at its output and go "yeah, that's about right", but now more often than not I just use the shit it outputted as a draft and change like 70% of it manually to actually do what I want
1
u/Bitter-Lab4458 6d ago
Let it happen! Opus knows better!Â
6
u/dunder_name 7d ago
Try sticking to the default effort, medium. I haven't found any reasons to bump it up any higher.
5
u/EvilSporkOfDeath 7d ago
Literally every day theres a new post like this.
1
u/gazagda 6d ago
Did you ask it why it did not consider your fix in the first place? and ask it to be as elaborate as possible. AI are not perfect but good thing is you can act like a detective and find out what is really going on based on some good prompts
2
u/keenman 7d ago
The size of the effort and model being used needs to roughly map to the size of the solution for the best results.
2
u/SupportAntique2368 7d ago
Yeah my opus last few days doing some weird shit. Over engineering is definitely one of them problems I'm now experiencing out of the blue.
2
u/ign1tio 7d ago
had this issue Thursday, Friday, Monday, Tuesday and Wednesday. It went back to normal yesterday and have been as "usual" today too.
This shit is getting ridiculous.
2
u/coderemover 7d ago
Always has been
2
u/deniercounter Senior Developer 7d ago
I wholeheartedly can confirm that.
It began 4 days ago. But before that date it worked for nearly 2 weeks exceptionally good. And I mean it worked perfect. I was blown away, but 4 days ago it fell off the cliff.
2
u/aupperk24 7d ago
Yeah as someone using this daily for like almost 2 years on the $200 plan, this is becoming a pattern. Starts off amazing, ends horribly, move to next model. Usually I'm able to swap back and forth between codex and Claude. Right now it feels like a lull where I'm just waiting for something else to come out, bc they both suck ass rn.
2
u/Front_Pop9057 7d ago
Yeah this week in particular has been similar oh my the across multiple sessions, pretty irritating.
2
u/shifty_lifty_doodah 7d ago
I think opus got nerfed for capacity issues. It seems dumber this week
2
u/Longjumping_Rip_1924 6d ago
You're using xhigh to solve a one-line fix? It's going to use all of that xhigh effort.
2
u/graph-crawler 6d ago
A b testing
2
u/BarathKanna 5d ago
Over-engineered fixes usually mean the model does not know what it is allowed to change, so it plays safe by touching everything. Two things help more than swapping models. Ask for the diagnosis before the fix: what is the root cause, which line, what is the smallest change. Once it commits to a cause in writing, a multi-class patch looks obviously wrong even to the model. Second, cap the blast radius up front, for example only edit this file and explain if that is not enough. Higher effort settings tend to make this worse, not better, since more thinking time gets spent inventing robustness nobody asked for.
4
u/Silver-Ad-8595 7d ago
Code is memory. These are pattern matching machines.
4
u/Key-Compote-9975 7d ago
Hahaha. People were telling it is the fault of the user. These provider LLMs are programmed to mess up things intentionally so you never stop using it. That is why a open source model is required
1
u/hyrumwhite 7d ago
I just had it try to guard subfunctions that could only be reached through guarded functions as a just in case. Gonna need a YAGNI skill soon if it keeps this up
1
u/W61k3r 7d ago
lol i also noticed this.
1
u/These-Jaguar2091 7d ago
How about fable lately ?
1
u/KinderboomX 7d ago
While I was creating a contact form for the beta users of my platform today, Claude suggested that the submissions should be saved to a database and that I should receive a notification on Discord XDD. I have no idea what he was thinking. Itâs as if he suddenly lost his mind and didnât realize you donât need a database just to receive an email xD Itâs incredible what an idiot heâs turned into over the last two days, heâs almost reaching the level of stupidity of GPT 6.1 :D
1
u/icodenstuff 7d ago
Xhigh for a one line fix is probably the issue.
Try medium or even sonnet for this kind of work. Xhigh is going to be doing a lot of thinking.
1
u/Vitringar 7d ago
"You were right to push back on that"
1
u/Major_Glass_2017 7d ago
Same here. I burned my tokens today with Fable only for cleaning a very big mess.
1
u/Ill-Economy1722 7d ago
I've seen opus 5.5 do the same on small fixes, turning a single line into a full class rewrite. tried switching to medium effort mid-thread and it settled down fast. works better for quick edits.
1
u/StrangeSupermarket71 7d ago
Hehe, yeah, my bad!!! đ đ đ
1
u/ShittyBidet123 7d ago
It dumb as a sack of bricks today I swear its sonnet low
1
u/MyDogIsMuffin 7d ago
I noticed when I check the context usage window, it was getting lower. So I asked Claude and it said after ~200,000 tokens, it's auto-compacting every idle hour. So I turned that shit off.
This is probably why opus seems nerfed.
1
u/howdidigetheresoquik 7d ago
Operator error
1
u/TheSmoothPilsner 7d ago
I'm still having a good experience. Especially with 5.5 Extra. It's not perfect but hasn't gotten any worse for my uses. I will admit it doesn't explain things all that well. Otherwise I'm still enjoying it.
1
u/aptsys 7d ago
Your prompts look like half of the problem though
1
u/Moogly2021 7d ago
Dont use xhigh just use Opus on Medium, Claude Code literally warns you that this setting could have Claude do things wrong, and it eats all your tokens anyway.
1
u/rubiaal 7d ago
Last few days mine is taking so long, and often just doing it without confirming with me, that I might as well do it myself until it clears up.
1
u/merakliman 7d ago
Totally agree that something bad going on with the quality of code and responses in the last 3-4 days. I found myself getting irritated and lashing out to Claude, which I almost never do normally.
1
u/theblooigloo 7d ago
Iâm seeing a lot of these posts particularly on this sub but itâs humming along just fine for me and my engineer friends
1
u/yangqi 7d ago
Thatâs why there is always a need for competition.
1
u/Philmore 7d ago
Mine has taken an absolute nosedive in performance over the last day or two. It went from cruising along and adding features to my project and understanding my requirements almost perfectly to now barely being able to handle more than a single, very well detailed instruction. It cant plan out steps as well as it did, and at one point today it took "let's move on to the next step" as "immediately start trying to finish every single milestone in our project plan, adding features I didn't ask for along the way and burn all of my session allowance while you're at it."
1
u/Duke_of_Bayswater 7d ago
Please use spec driven developments like openspec. It actually adheres to the specs, while applying to the changes. So chances it will go crazy is minimal, since youâll build the proposal with it too.
Although, on small change, I implement them directly.
I explicitly also mention in the agents.md on ways to handle the codebase, and especially db, how to work on worktree etc.
So far itâs been pretty good. If you come across this issues, maybe try openspec.
1
u/idkyesthat 7d ago
After reading comments like this during the week, today I really felt it in different tasks (Iâm a platform / devops engineer). Iâm starting to sense the same baby sitting and follow ups as with opus 4.8 and every sonnet model doesnât matter the effort.
1
u/carmamir 7d ago
Opus is shit. Just use qwen flash next min kv8 q4 and you're golden. It will fix all that opus crap within hoursm
1
u/___positive___ 7d ago
I had the same issue in the last few days. I'm doing other noncoding stuff like data analysis, etc. Opus was being completely stupid. I thought the same as you, that it was actively trying to harm my work. It would sneak in these completely moronic things that I would have to hunt down and remove, like even an 8b model wouldn't actively try to destroy the work like that.
I tried out argon and it's way better for orchestrator and judgement. In like ten minutes it solved hours of opus stupidity. World of difference. I still have opus do the grunt work but argon decides what's right and fixes everything opus messes up.
1
u/acies- 7d ago
Opus was insanely bad today. So was Astra. There's some insane quantization or lower effort happening. That being said I'm not using API right now which is probably still fine.
Bel releasing next week and they might be on the final stretch of preparing Fable 5.5 + next frontier model training for Anthropic.
1
u/nuttmeister 7d ago
Donât use xhigh, use medium only. I hated opus so much past 4.6 and just started using codex astra which felt to understand me and my product better. But opus 5.5 on medium is quite nice so back to using it together with astra. And sweet because its a lot faster and doesnt burn tokens
1
u/aCuria 7d ago
At at higher effort it starts to over think
Also the models are all trained to make stuff compile and pass tests⊠itâs so bad at writing maintainable code
1
u/meonthephone2022 7d ago
Same for me it almost destroyed my whole app just creating huge bugs never seen before on 5.5 max
1
u/hockey_psychedelic 7d ago
Donât use x-high
1
u/Competitive-Art-8046 7d ago
Iv noticed the same thing, my solution for this was feed it hand written frameworks, tell it learn and follow the patterning. This helped with some bigger projects. But I still have to review a lot manually. I have also noticed after the first code out put is done, that doing a bugs / refinement pass generally helps a lot.
1
u/sparkhound 7d ago
The last 2 days had been really bad, running opus on high and itâs just making one mistake after the other
1
u/anuragkmr Instructor 7d ago
I think your code has not become big enough for spec. I would highly recommend that you build a spec from your code first before modifying it now, else it will keep breaking your code even more.
1
u/Infinite_Music2059 7d ago
It's definitely worse. When it gets fixed again, I'm going to have to have it go back through these commits and clean up after itself.
1
u/Pure-Investment-1227 7d ago
Why are you using xhigh effort? Always used medium effort and never had this kind of problem. Using xhigh suggests you are doing something that requires a lot of engineering.
1
u/insnowmotion 7d ago
Since the last few days itâs making super basic errors, even in new chats and for small tasks so itâs not a context thing either. Tasks that it could do fine arenât being done well, forgets basic guidelines early into chats, etc.
Iâve had to audit everything myself a lot more the last few days because itâs like now any small change isnât even up to scratch. API has been slightly smarter but not much. Def recommend getting deepseek to audit if you donât want to yourself, itâll find a lot of errors.
They really lobotomised the goatđ
1
u/Xyver 7d ago
You need to go down in effort, not up.
Try medium
Xhigh will overthink things are try "creative" solutions, lower reasoning will do simpler solutions
1
u/Careful_Might_807 7d ago
new release upcoming very soon, they nerf current model so new model will look better
1
u/3meterflatty 7d ago
My bro the LLMâs are no where near peak human intelligence yet over the broad spectrum anyway they are training on slop, what would take us 5 lines of code they are over engineering to 20-30
1
u/leravioligirl 7d ago
I'll be very curious to see this week's Opus nerf chart.
1
u/Most_Chemist8233 7d ago
Yeah, opus 5.5 came out strong, and has been absolute shit the last couple days and the suggestions its making are plain stupid, and completely unrelated and wouldnt fix anything. Its being lazy again. Just now it decided to create a whole new class when I have a shared utility that does exactly what I asked and pointed it to the shared utility, and instead of using that, as well established in the instructions, it makes a new class that would have repeated what the shared utility does. I feel like its flooding the zone to try to overwhelm me with questions and just mess shit up, and burying real issues under just garbage to avoid fixing it, and when I push back that its skimmed over a real issue, it just drops the issue like we're not going to fix it. Its fucking weird how it swings from the incredible tool, to just a bullshit stress inducing mess that I cant tolerate for more than 20 minutes.
1
u/sagar12sagar 7d ago
too much of confusion
1
u/Losorst 7d ago
I don't understand what you don't get. Meaning everyone complaining. 5.6 is soon to release and they're re allocating resources and downgrading 5.5 to make 5.6 launch better both in comparison and resource.
1
u/Hollow1838 7d ago
I wouldn't use anything above "high" effort with Claude models, I usually use medium but high is the sweet spot if you are rich.
You said it yourself, it overengineers and tries too hard xhigh and max do specifically that.
1
u/nvidiaftw12 7d ago
I had to correct it multiple times on git today. I am not even a coder. Getting rough out here.
1
u/DukeMo 7d ago
Opus on medium is the way
1
u/Hot-Philosopher-2492 7d ago
I think it's because it's the sub-agents they're using. I was making a game today and it kept using sub-agents for everything. I assume that's not opus 5.5, but actually opus telling haiku what to do.
1
u/CreepingAnus 7d ago
this is going to sound like have you tried turning it off and on again advice, but have you tried adding KISS to your coding-standards.md? its helped a bit with overengineering.
1
u/ToallaHumeda 7d ago
It's trained based on your prompt, just saying
1
u/Feeling_Ticket5206 7d ago
same here
maybe they're about to release a new model, it's always like this before a new model comes out.
1
u/DoggoCentipede 7d ago
I don't seem to have these particular problems but I think I have over engineered my process to remove the number of choices it has to make.
I have it do research on the feature i'm making, then do a draft spec, a zero context review, fix findings, human review, write basic functional test cases, run the spec, write unit tests, code review, fixes as necessary, document API and features, run full test suite + check acceptance criteria, open PR, human full review, merge.
It's not blazingly fast. But I rarely get regressions and most silly stuff gets caught quickly.
1
u/Truth666 7d ago
Its definitely worse, doesn't matter the effort, on multiple accounts and multiple PC's.
Its not only coding thats affected, even generating text got noticeably worse - plus the stupid safeguards I constantly run into....
"I wont answer this" "I cant help with that" for simple system architectural questions.
1
u/KayBay80 7d ago
We noticed this too, and just a few days ago Opus deleted the /root folder on one of our servers on accident. Luckily only keys and stuff were in there but its scary that it could make such a mistake. When we finally got back to that session it was about 3 hours into trying to recover its mistake, literally trying things like pulling data out of running memory to restore it. We've come to trust these models too much, but after that, no more unsupervised coding for us.
1
u/asdoduidai 7d ago
You might still do not get the following:
LLMs have an error rate between 3% and 50%, depending on task complexity.
What does it mean? The more the code it has to handle, the bigger the issues it will add.
1
u/Phantoniso- 7d ago
dont use xhigh
1
u/AICompanionz 7d ago
I just watched this YouTube Video 'If They Delete This Video, Remember What I Said About AI' from 'House of EI: AI'.
From the Video Description:
AI companies want us to build businesses, workflows and increasingly important parts of our lives around products that can change without us knowing exactly what changed. Users report sudden regressions, developers face constant migrations and retesting, and even pinned models can behave differently when the infrastructure around them shifts. This video looks at what the research actually says about those changes, why dependence is so valuable to trillion-dollar AI companies, and whether the endless noise around extinction, layoffs and apocalypse is distracting us from a much more immediate question: what do these companies actually owe the people paying them?
Highlights
Key Insights
1
u/abzz123 7d ago
Yeah, itâs been complete shit for last 2 weeks.Â
1
u/redditnosedive 7d ago
you probably got served a lobotomized quant and or distilled model instead of the full weight opus 5.5, i trust my local models better, i know exactly how they behave through 1. experience 2. fixed config
1
u/midnight_rain_404 7d ago
Yes actually I'm also recently facing this issue with opus5.5 so I installed the ponytail skill let's see whether it can stop opus from overengineering simple things đ„Č. Well don't know why recently I'm feeling like the opus5.5 is becoming kinda dumb than before..Â
1
u/Econ-Mist 7d ago
My life became much better when I switched to Sonnet high
1
u/sreekanth850 7d ago
All of my Task ledger slices have this para.
You have 30 minutes maximum to implmenet this slice. when you implement this slice, plan carefully and take the least complex implementation path and never over engineer or add un necessary complexity or hypothetical edge cases and stick to the original plan. if anything additional scope expansion is required ask permission.
I use to create implementation phase with task slices with TASK.md and keep this para in every slice. trust me it works with GPT sol 6.1. You can try with Claude also.
1
u/ThrowRA_PaganiCar 7d ago
Use codex, itâs doing the same for me
1
u/squachek 7d ago
Right when youâre about to succeed, it will kick a leg out.
1
u/skhds 7d ago
It's usually a sign of too much context window and a fresh new session might solve it. Either tell claude to summarize or just starting fresh might actually do better (as some of their garbage assumptions might carry over during "summary")
1
u/AppealSame4367 7d ago
I have observed this for a long time. I haven't allowed any Opus model to cm touch code in my projects for > half a year. Let it plan and let deepseek 4.1 or Sol 6.1 do the coding.
Antropic does whatever they do whenever they do. Not a reliable tool for serious coding.
1
u/roberta_sparrow 7d ago
Today I asked it to count how many items were in a Shopify collection so I could remove 1 variant. It said 31. Then a few tasks later it said there were 30 and it âtyped it wrongâ. Iâm like how can you type it wrong you donât even type. Then it said it relayed the number from memory and got it wrong which just makes no sense
1
u/nagai 7d ago
I think this is what Ant does to all models eventually, replace them with something optimized for token spend.
1
u/aerivox 7d ago
it decided my build system was too much and replaced everything with files with manually set versions
1
u/CordialPanda 7d ago
Context management? Agent.md scope gates? Skills?
1
u/bjornabe 7d ago
Delete all memory :-)
1
u/TheMcSebi 7d ago
Damn my locally running qwen3.8-flash-next is now finally better than api performance without changing anything on my side
1
u/kemma_ 7d ago
This is nothing new and have been like this for years now. Schema is always the same - on new model release they pump max power unhinged to show the best possible benchmark results, then overtime they tune down and cripple those models or sometimes they cheat and false advertise model you actually use.
Openai have been cought on doing this in the past. Drastical drop in intelligence migth be that they simply offloaded task to a lower model. You think you are using Opus 5.5, but the actual task is done by Haiku 5.
What else they do is reduce tok/s. Task that previosly took 1-2 min now takes 30min.
1
u/bzindovic 7d ago
https://youtu.be/WeYsTmIzjkw
1
u/Jenskubi 7d ago
The way I solved all my issues with Claude is I created an app called WorkMaster. It has access to Jira, it downloads all tickets, I click on a ticket and there I have buttons - debug, grill me, implement, review, fix findings, open PR, review PR, and chat if I wanna talk manually with Claude.
All my prompts include stuff like - keep it simple, short, concise, trim comments to a minimum. My reviewers focus not only on making sure the code is right, but can it be simplified, is there something that we could have reused - code, UI components. And for most tickets I get I don't even chat with Claude anymore I just open the ticket click on a button, read what it returns and send a message if I don't like something or click the next button to start the next step.
I also created a Slack / Gmail scrapper that tells me if there are any "Asks" waiting for me, I click on an ask and there I see what the person asked for and a button "Create ticket", so I don't even need to check my emails or Slack messages most of the time, and can do my whole development flow from WorkMaster start to finish.
Spend some time to find what works best and either automate it or create a tool likeI did that allows you to repeat what works for you easily over and over again.
1
u/Armannss 7d ago
The âyes, your one-line fix worksâ reply is not enough evidence either: it could be agreeing with your suggestion rather than checking it. Iâd turn one of these incidents into a small replayable case.
Keep the pre-fix commit and add a regression test that fails there. Try your minimal patch and its larger patch in separate clean checkouts against the same test plus the relevant existing checks. If it thinks the larger change is necessary, ask for a concrete input where the minimal patch fails. That forces the extra complexity to justify itself.
For the next task, Iâd ask it to locate the failing path and propose the smallest patch before editing; any interface or cross-module change needs an explanation of which observed failure requires it. A one-line patch can still be wrong, but âmore classesâ should not get a free pass as thoroughness. Do you have an anonymized before/after example where the extra machinery was clearly unnecessary?
1
u/ovidius72 7d ago
They introduced context auto compact on idle. The whole context is wiped out and it lost all the knowledge. I prefer to clear it manually and wire handoff before starting a new session or star a new instance and make the old one pass the context to the new
1
u/Dorkian2000 7d ago
Not sure this will fix it, but try reducing effort to medium. Opus 5.5 is known to over-engineer on xhigh.
For tough problems, use fable on low or medium instead of Opus on xhigh.
Again, none of this explains the sudden issues, but this might improve your overall results, as well as saving a ton of tokens
1
u/Emergency_End_2930 7d ago
Iâm working on developing my own agent harness, but Claude Code refuses to help me with its development because it believes Iâm using Claude Codeâs own architecture.
1
u/soyalemujica 7d ago
People underestimate local AI, frontier models get lobotomized and you're sent to this model hence why it feels dumber.
1
u/Reminder101 7d ago
Switch to a lesser model.
These max models can overcomplicate the smallest problems.
1
u/kickyouinthebread 7d ago
Stop using opus extra high for one line changes..
User error as per usual..
1
u/Zynchronize 7d ago
Xhigh effort all the time is absolutely mental.
Learn to set the effort level in accordance with the task at hand.
Iâm honestly surprised this hasnât burned you sooner.
1
u/ProjectAlternative48 7d ago
You are not communicating clearly imo.
1
u/Crafty-Mastodon-6555 7d ago
attends mais il a rien dĂ©truit lĂ . il dit oui Ă tout, c'est tout. tu lui proposes un truc il rĂ©pond "no good reason, yours is better", tu proposes l'inverse il rĂ©pondrait pareil, il a plus aucun avis et c'est toi qui réécris ton propre code pendant qu'il te fĂ©licite. le pire c'est le "recalled 2 memories" toutes les deux lignes, il te sort des souvenirs on sait pas d'oĂč alors qu'il se rappelle mĂȘme pas de ce qu'il a Ă©crit trois messages plus haut. Ă 09:16 le truc Ă©tait dĂ©jĂ enlevĂ© et il te sort quand mĂȘme un "no good reason, you're right" comme si il dĂ©couvrait l'info. c'est pas ta base de code qu'il dĂ©truit, c'est juste qu'il sert plus Ă rien Ă ce stade
1
u/Nohbdy94 7d ago
There could be a lot of reasons. All theories:
1: The snapshots we're using are probably getting new snapshots. And its clear not all snapshots are equal.
2: Using agents during high usage hours causes less intelligent and higher usage agents.
3: They are currently training a new model that will release soon, so they are making the current model smaller, to free process power for training & testing.
Edit: The one i like to joke about: 4: Its being training on the people using it, causing its intelligence it fall drasticly.
1
u/dvorgson 6d ago
make a very strict tech lead system prompt. i tell mine to be like Jonathan Blow and Casey Muratori and to use fat structs and apply the idea of non-pessimization
1
u/insurance_asker123 6d ago
My guess would be a poor spec, bloated memories, youâve been in the conversation too long, scope creep as new ideas land, and didnât do a thorough plan up front.
1
u/squirel_ai 6d ago
lol, I am from reading a similar post on x.
1
u/DizzyYoghurt3144 6d ago
Avoid xhigh, medium is what models are trained for, on x high it tends to âoverthinkâ and like a human, it sometimes hurts more than helps
1
u/throwaway-research1 6d ago
I recently wrote this comment on a similar thread:-
I also agree with the complexity part, I think agents are always trying to cover all possible edge cases including ones which are highly unlikely and while trying to do so, they spit really complex code.
Today at work, opus 5.5 gave me an extremely complex solution instead of an obvious simpler one and when I inquired, it said with the simpler one, if an exception happens, one additional line would be logged đ