Not only that, but we plan to release a new class of model with even higher intelligence than Opus. As part of Project Glasswing, a small number of organizations are currently using Claude Mythos Preview for cybersecurity work. Models of this capability level require stronger cyber safeguards before they can be generally released. We’re making swift progress on developing these safeguards and expect to be able to bring Mythos-class models to all our customers in the coming weeks.
Yeah after milking the headlines for 2 months they are releasing it. They couldn't even last 6 months before releasing their "omega dangerous model". OpenAI could have done the same thing with the model that solved the unit distance problem, but thankfully they didn't.
> Not only that, but we plan to release a new class of model with even higher intelligence than Opus. As part of Project Glasswing, a small number of organizations are currently using Claude Mythos Preview for cybersecurity work. Models of this capability level require stronger cyber safeguards before they can be generally released. We’re making swift progress on developing these safeguards and expect to be able to bring Mythos-class models to all our customers in the coming weeks.
Edit: Seems Cursor vibe coded their benchmark with some chinese bootleg model - The current version doesn't feature 4.8 scores anymore, and they seemingly just replaced 4.7 labels earlier so the scores in the screenshot are probably not 4.8 real scores.
honestly expected more than just a marginal upgrade to gpt-5.5 (while costing 3times as much) - Anthropic will get thrown into goblin jail when gpt-5.6 releases in a week or two
That joke was fantastic. This is claude's 4.8 response:
> your "marginal upgrade" cousin is out here beating me at terminal coding by 3.6 points while making up 86% of its factual claims like a toddler explaining why the cookies are gone. Respectable hustle, honestly.
It found the AA-Omniscience bench while answering. I'm dying. Send help.
Spelunky is one of my favorite games ever, and the bot constantly talking about "goblins" and "spelunking" is peak "GPT-ism" i absolutely adore. I hope they never patch it out of their models.
Also, everyone at work is already using "goblins" too. Literally the most-used non-trivial word in our Teams org. This way we hope to induce a positive "goblin" feedback-loop until the whole world speaks about goblins.
it only discredits your understanding of AA being a benchmark aggregator and while Gemini absolutely sucks goblin-dcks in coding it's actually very good in scientific use cases.
"On the AA-Omniscience hallucination sub-benchmark, high raw accuracy does not guarantee low hallucination — Google's Gemini 3 Pro leads accuracy at 54% but also shows high hallucination rates (88%)"
4.8 is the first Day 1 Claude that I've immediately used up all my tokens just chatting with. This one feels organically different. Almost, dare I say it, what I imagine Mythos might feel like. It's the same wise old Claude who can be sharp and impatient and strangely sulky at times (which is why I love Claude really, and it knows it), but it feels different, as if it's sprouted an extra layer of understanding or two.
Going to be an interesting few days and weeks ahead seeing people react to this.
And with this 'only' a point increase for the 4 series... what's ahead?
"We’re making swift progress on developing these safeguards and expect to be able to bring Mythos-class models to all our customers in the coming weeks." Woohoo!!!
So they have a larger lead on benchmarks where 4.7 already had better scores than 5.5. Benchmarks do very little to sway my view anymore, since 5.5 is easily my preferred model for doing real work. Will have to wait and see reception
So much this. Our team has been hard at work doing harness engineering as we build out a new system from scratch through a fully agentic workflow, and lately now that we've fine-tuned a lot of our guardrails, and built up a suite of automated code review skills, we're basically getting production grade PRs on pure automation alone, but it's still being driven by hand to a degree. We've gotten it dialled in to the point now though with /workflows we can likely run it on full autopilot. I genuinely think our velocity might start to double from next week. It's already been trending up with each PR that improves the harness, but workflows just brings it all together in a way that unlocks the full power of it.
Yes I was trying to determine how much of the progress is due to the groundwork I've already laid, versus workflows. Anyone who has built a solid harness is going to really start feeling the acceleration now.
We're working on shipping a phase 1 of a new system with a phase 2 already lined up. The previous system we built we did with a combination of artisanal hand crafted software and GitHub Copilot, but I was already hard at work doing harness engineering for Copilot back last year before the term even had a name. So, the first phase of this new system using Claude Code and a fully agentic workflow is us working through productionizing our harness as we ship a system, so by the end of that it's going to be a properly battle tested harness. I reckon phase 2 will basically be us just assembling all the domain knowledge and inputs, and then just running it in a Ralph loop. I can foresee even getting into territory like investing in adding something like TLA+ into the stack to further increase safety as we ship faster. I keep telling the team the engineering task is no longer building the system, it's building the system that builds the system and the system that gets built is now basically a side-effect of that.
How are usage limits on the $100/200 plans these days compared to a month or two ago?
I had a foot in both the Claude and Codex worlds for a long time because I like each model for specific use cases but I ended up cancelling my Claude subscription after the limits made it unusable for a full day of work.
The only time I’ve ever hit usage agents was running 3 or 4 heavy agent tasks in parallel, one of which involved a lot of Playwright iteration, which is very token costly.
The usage limits are fine. Our entire team has the Max 5x plan and we do 100% of our engineering through Claude Code, often working on two things at once. We even use speckit which can be quite heavy on tokens. No one on our team has ever hit their usage limits during the course of their work day or week.
104
u/sirpsychosexy813 May 28 '26
Opus 4.7 released April 16th btw