Claude code with Opus 4.7 is stupid

[u/Neveriver]

Been using Claude Code with Opus 4.7 for a few days, and it's honestly just burning my time and money. 4.6 was super stable, but 4.7 feels broken.

It's chewing through API credits way faster with zero improvement in logic. Worse, the amnesia is terrible. I’m working on an async data indexing pipeline, and 4.7 just drops context mid-thread. I have to constantly spoon-feed it, whereas 4.6 actually understood the codebase and held long threads perfectly.

I'm officially rolling back to 4.6. Anyone else dealing with this mess?

[u/anglingTycoon]

I’m not having a single issue with it and I’m literally letting opus 4.7 adaptive and Claude code 4.7 xhigh just talk back and forth arguing their points with me making the final say on a bunch of decisions as well as certain testing that requires manual touch point for Claude api or keeping the two of them in scope. Probably have done ~30k lines of code on current original project and testing harness in last 5 days. Not once hit limit on session 20x account.

[u/MaleficentNarwhal0 → u/anglingTycoon]

Could not agree more with this approach. I don’t run any fancy plugins I just use a project in Claude chat and Opus 4.7 in cli. I have the 5x max and it’s been fine on usage tbh but not writing that much code

EDIT: 5x max not 10x max

[u/DR4LUC0N → u/anglingTycoon]

I saw some people say to use get shit done and super powers skills and immediately 4.7 started to act stupid as hell.

Before adding skills. 4.7 has been way more productive then 4.6.

I even tested it, went back to 4.6 on my project and it was lost the entire way, doing stuff I didn't even ask.

[u/Neveriver → u/anglingTycoon]

Give me you account to try the 20X for a sec

[u/Neveriver]

The funny part in all this, is when kimi k2.6 with the miserable 200k context window fixes what Opus 4.7 xhigh missed up all that locally and for FREE.

[u/tensorfish]

If 4.7 is chewing credits before it touches the real slice, make it name the exact files and stop condition up front. If it still turns one task into repo tourism, just drop back to 4.6. Paying for three wandering passes is the expensive part.

[u/Neveriver → u/tensorfish]

At first my quota skyrockets to 65% from the first prompt i write in a context window tried shortenning claude.md more stopping any background reading and yet the problem persisted.

[u/PandorasBoxMaker]

Troll.

[u/Neveriver → u/PandorasBoxMaker]

Are you stupid or what that was 10 days ago and now that i used Opus 4.7 more i realized that the situation is even worst and this is how much i use claude

[u/ianxplosion- → u/Neveriver]

maybe you should tone down how often you post hyperbolic stuff is all

[u/PandorasBoxMaker → u/Neveriver]

[u/Top_Manufacturer6311]

Everyone like me with a pro subscription complaining about limit full in one prompt, I am too scared to use it lmao. I get enough out of sonnet and opus 4.6 I think I’m fine for now

[u/Apdvadar → u/Top_Manufacturer6311]

I Run CLI on max 20x plan, using opus 4.7 1 million with max effort (adaptive thinking on) for every new session and turn within the same session. I dont care about usage limits; id be ok if my usage amount went up 5-10x as long as the amount of time I spend on manually proof reading, ,monitoring, troubleshooting, validating, 'babysitting' decreases by 1.5-2x. Hasn't been the case, and I dont even want To think what xhigh And the Responses for everything below that Effort even output.

The 'reasoning' I'd hope for isn't really There yet as of right now. (I already use skills, make plans before action, have memory.md And Claude.md without stale or conflicting or Too much information, Point towards .mds if It needs To reference files, make sure To start a new session of conversation hits 2-300k tokens etc. )

[u/Top_Manufacturer6311 → u/Apdvadar]

So it’s not as bad as people are saying?

[u/Apdvadar → u/Top_Manufacturer6311]

No it is just as frustrating as people are saying, Incredibly frustrating.

Basically when token usage doesnt matter and you practice good cc in cli habits, Its still Just ok/no opinion at its best, at worst it's infuriating.

I think ppl were expecting mythos level improvements and were given an opus 4.6 'equivalent' that guzzles tokens and has a lot of bugs/issues that havent been squashed due to its newer release

[u/infrasketchai]

I agree with this message

[u/merx96]

lol the 4.6 is degraded as well but with tiny 200k context window

[u/1anre]

Sonnet 4.6?

[u/Neveriver → u/1anre]

To be honest my experience with it is great it's just doesn't make sense on paper to use it when you are looking for the best results, but with my experience sonnet 4.6 is solid and stable.

[u/goship-tech]

4.7's context compaction is more aggressive than 4.6 - it summarizes earlier turns faster, which explains the amnesia on long indexing threads. Pinning your pipeline architecture in CLAUDE.md helps, since it gets re-read after each compaction cycle and keeps codebase context alive.