This is the 7th advert on the front page right now. It's ridiculous
Claude Opus 4.7
451–460 of 1001 posts
Re: Claude Opus 4.7
#452Too late, personally after how bad 4.6 was the past week I was pushed to codex, which seems to mostly work at the same level from day to day. Just last night I was trying to get 4.6 to lookup how to do some simple tensor parallel work, and the agent used 0 web fetches and just hallucinated 17K very wrong tokens. Then the main agent decided to pretend to implement tp, and just copied the entire model to each node...
I switched to Codex and found it extremely inferior for my use case. It is much faster, but faster worse code is a step in the wrong direction. You're just rapidly accumulating bugs and tech debt, rather than more slowly moving in the correct direction. I'm a big fan of Gemini in general, but at least in my experience Gemini Cli is VERY FAR behind either Codex or CC. It's both slower than CC, MUCH slower than Codex,…
What is your use case? I read comments like this and it's totally opposite of my experience, I have both CC Opus 4.6 and Codex 5.4 and Codex is much more thorough and checks before it starts making changes maybe even to a fault but I accept it because getting Opus to redo work because it messes up and jumps in the first attempt is a massive waste of time, all tasks and spec are atomic and granularly spec'd, I'd say 30% of the time I regret when I decide to use Opus for 'simpler' and work
Re: Claude Opus 4.7
#453Earlier quoted context omitted.
It's likely hiding the model downgrade path they require to meet sustainable revenue. Should be interesting if they can enshittify slowly enough to avoid the ablative loss of customers! Good luck all VCs!
They have super sustainable revenue. They are deadly supply constrained on compute, and have a really difficult balancing act over the next year or two in which they have to trade off spending that limited compute on model training so that they can stay ahead, while leaving enough of it available for customers that they can keep growing number of customers.
But do they? When was the last time they declined your subscription because they have no compute?
Re: Claude Opus 4.7
#454I hope this will fix up the poor quality that we're seeing on Claude Opus 4.6 But degrading a model right before a new release is not the way to go.
I wish someone would elaborate on what they were doing and observed since Jan on opus 4.6. I’ve been using it with 1m context on max thinking since it was released - as a software engineer to write most of my code, code reviews + research and explain unfamiliar code - and haven’t notice a degradation. I’ve seen this mentioned a lot though. I have seen that codex -latest highest effort - will find some important edge…
I don't use it for coding, but I do use it for real world tasks like general assistant.
I did notice multiple times context rot even in pretty short convos, it trying to overachie and do everything before even asking for my input and forgetting basic instructions (For example I have to "always default to military slang" in my prompt, and it's been forgetting it often, even though it worked fine before)
Re: Claude Opus 4.7
#455noticing sharp uptick in "i switched to codex" replies lately. a "codex for everything" post flocking the front page on the day of the opus 4.7 release
me and coworker just gave codex a 3 day pilot and it was not even close to the accuracy and ability to complete & problem solve through what we've been using claude for.
are we being spammed? great. annoying. i clicked into this to read the differences and initial experiences about claude 4.7.
anyone who is writing "im using codex now" clearly isn't here to share their experiences with opus 4.7. if codex is good, then the merits will organically speak for themselves. as of 2026-04-16 codex still is not the tool that is replacing our claude-toolbelt. i have no dog in this fight and am happy to pivot whenever a new darkhorse rises up, but codex in my scope of work isn't that darkhorse & every single "codex just gets it done" post needs to be taken with a massive brick of salt at this point. you codex guys did that to yourselves and might preemptively shoot yourselves in the foot here if you can't figure out a way to actually put codex through the ringer and talk about it in its own dedicated thread, these types of posts are not it.
Re: Claude Opus 4.7
#456I'm finding the "adaptive thinking" thing very confusing, especially having written code against the previous thinking budget / thinking effort / etc modes: https://platform.claude.com/docs/en/build-with-claude/adapti... Also notable: 4.7 now defaults to NOT including a human-readable reasoning token summary in the output, you have to add "display": "summarized" to get that: https://platform.claude.com/docs/en/build-…
Note that for Claude Code, it looks like they added a new undocumented command line argument `--thinking-display summarized` to control this parameter, and that's the only way to get thinking summaries back there.
VS Code users can write a wrapper script which contains `exec "$@" --thinking-display summarized` and set that as their claudeCode.claudeProcessWrapper in VS Code settings in order to get thinking summaries back.
Re: Claude Opus 4.7
#457Here you go folks:
https://www.svgviewer.dev/s/odDIA7FR
"create a svg of a pelican riding on a bicycle" - Opus 4.7 (adaptive thinking)
Re: Claude Opus 4.7
#458This comment thread is a good learner for founders; look at how much anguish can be put to bed with just a little honest communication. 1. Oops, we're oversubscribed. 2. Oops, adaptive reasoning landed poorly / we have to do it for capacity reasons. 3. Here's how subscriptions work. Am I really writing this bullet point? As someone with a production application pinned on Opus 4.5, it is extremely difficult to tell ap…
Good shout. Wish they were more transparent about these 3 things.
Re: Claude Opus 4.7
#459Earlier quoted context omitted.
> Still trying to get a decent pelican out of this one but the new thinking stuff is tripping me up Wouldn't that be p-hacking where p stands for pelican?
Input: I want to wash my car. The car wash is 50 meters away. Should I walk or drive? Output: Walk. It'll take you under a minute, and driving 50 meters barely gets the engine warm — plus you'd just have to park again at the other end. Honestly, by the time you started the car, you'd already be there on foot. --- I asked it to figure out why it made the mistake: "Physical/spatial common sense. Exactly what just happe…
Well, at least we know that's one gotcha/benchmark they aren't gaming.
Re: Claude Opus 4.7
#460I'm finding the "adaptive thinking" thing very confusing, especially having written code against the previous thinking budget / thinking effort / etc modes: https://platform.claude.com/docs/en/build-with-claude/adapti... Also notable: 4.7 now defaults to NOT including a human-readable reasoning token summary in the output, you have to add "display": "summarized" to get that: https://platform.claude.com/docs/en/build-…
Its especially concerning / frustrating because boris’s reply to my bug report on opus being dumber was “we think adaptive thinking isnt working” and then thats the last I heard of it: https://news.ycombinator.com/item?id=47668520
Now disabling adaptive thinking plus increasing effort seem to be what has gotten me back to baseline performance but “our internal evals look good“ is not good enough right now for what many others have corroborated seeing