I was using Opus 4.7 just yesterday to help implement best practices on a single page website. After just ~4 prompts I blew past my daily limit. Another ~7 more prompts & I blew past my weekly limit. The entire HTMl/CSS/JS was less than 300 lines of code. I was shocked how fast it exhausted my usage limits.
Which plan are you on? I could see that happening with Pro (which I think defaults to Sonnet?), would be surprised with Max…
Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
121–130 of 620 posts
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#122We dropped Claude. It's pretty clear this is a race to the bottom, and we don't want a hard dependency on another multi-billion dollar company just to write software We'll be keeping an eye on open models (of which we already make good use of). I think that's the way forward. Actually it would be great if everybody would put more focus on open models, perhaps we can come up with something like the "linux/postgres/git…
>we don't want a hard dependency on another multi-billion dollar company just to write software One of two main reasons why I'm wary of LLMs. The other is fear of skill atrophy. These two problems compound. Skill atrophy is less bad if the replacement for the previous skill does not depend on a potentially less-than-friendly party.
It was an experiment to see if I could enter a mature codebase I had zero knowledge of, look at it entirely through an AI, and come to understand it.
And it worked! Even though I've only worked on the codebase through Claude, whenever I pick up a ticket nowadays I know what file I'll be editing and how it relates to the rest of the code. If anything, I have a significantly better understanding of the codebase than I would without AI at this point in my onboarding.
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#123Earlier quoted context omitted.
Yes, you certainly can argue that, but you'd be wrong. The primary selling point of LLMs is that they solve the problem of needing skill to get things done.
That is not the entire selling point - so you are very wrong. You very much decide how you employ LLMs. Nobody are keeping a gun to your head to use them. In a certain way. Sonif you use them in a way that increase you inherent risk, then you are incredibly wrong.
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#124Earlier quoted context omitted.
How do you justify the API and web UI versions of 4.7 refusing to solve NYT Connections puzzles due to "safety"? https://x.com/LechMazur/status/2044945702682309086
To be fair, reading the New York Times is a safety risk for any intelligent life form these days. But still.
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#125Our default topology is a two-agent pair: one implementer and one reviewer. In practice, that usually means Opus writing code and Codex reviewing it.
I just finished a 10-hour run with 5 of these teams in parallel, plus a Codex run manager. Total swarm: 5 Opus 4.7 agents and 6 Codex/GPT-5.4 agents.
Opus was launched with:
`export CLAUDE_AUTOCOMPACT_PCT_OVERRIDE=35 claude --dangerously-skip-permissions --model 'claude-opus-4-7[1M]' --effort high --thinking-display summarized`
Codex was launched with:
`codex --dangerously-bypass-approvals-and-sandbox --profile gpt-5-4-high`
What surprised me was usage: after 10 hours, both my Claude Code account and my Codex account had consumed 28% of their weekly capacity from that single run.
I expected Claude Code usage to be much higher. Instead, on these settings and for this workload, both platforms burned the same share of weekly budget.
So from this datapoint alone, I do not see an obvious usage-efficiency advantage in switching from Opus 4.7 to Codex/GPT-5.4.
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#126We dropped Claude. It's pretty clear this is a race to the bottom, and we don't want a hard dependency on another multi-billion dollar company just to write software We'll be keeping an eye on open models (of which we already make good use of). I think that's the way forward. Actually it would be great if everybody would put more focus on open models, perhaps we can come up with something like the "linux/postgres/git…
>we don't want a hard dependency on another multi-billion dollar company just to write software One of two main reasons why I'm wary of LLMs. The other is fear of skill atrophy. These two problems compound. Skill atrophy is less bad if the replacement for the previous skill does not depend on a potentially less-than-friendly party.
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#127Earlier quoted context omitted.
qwen3.5/3.6 (30B) works well,locally, with opencode
Mind you, a 30B model (3B active) is not going to be comparable to Opus. There are open models that are near-SOTA but they are ~750B-1T total params. That's going to require substantial infrastructure if you want to use them agentically, scaled up even further if you expect quick real-time response for at least some fraction of that work. (Your only hope of getting reasonable utilization out of local hardware in sing…
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#128Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#129Earlier quoted context omitted.
Is this sort of setup tenable on a consumer MBP or similar?
For a 30B model, you want at least 20GB of VRAM and a 24GB MBP can’t quite allocate that much of it to VRAM. So you’d want at least a 32GB MBP.
Re: Anonymous request-token comparisons from Opus 4.6 and Opus 4.7
#130We dropped Claude. It's pretty clear this is a race to the bottom, and we don't want a hard dependency on another multi-billion dollar company just to write software We'll be keeping an eye on open models (of which we already make good use of). I think that's the way forward. Actually it would be great if everybody would put more focus on open models, perhaps we can come up with something like the "linux/postgres/git…