WASDx

Sounds like a hypothesis to me.

I think the top models on that one have minimum goodwill and rejects refunds.

AA published their article on Carbon now at the same time so it's absolutely coordinated.

AA updated their index version yesterday. For sure Google waited for that update so they could be #1.

1. "Building on Gemini 4 Argon". 2. Same price. 3. Relatively short time between releases.

Makes me think it's further post-training of the same model.

It's broken for me in Firefox, worked with Chrome.

Their benchmark result table is broken in Firefox.

Great benchmark!

I believe effort can mean both "solve harder problems" and "produce more stuff". I mostly don't want more stuff than I asked for, so a capable model at lower effort can indeed be the wiser choice. Faster response too.

I believe it's Astra quantized. It was briefly named astra-lite.

When you see these absurd numbers, they are re-counting cached input for every turn. So a simple tool call when your context size is at 500k counts as another 500k to the sum.

Total Opus 5.5 token usage on OpenRouter last week is 5000B, presumably not counting cached input.

How do you validate the functions are correct? I did something similar, letting it (mostly deepseek 4.1) translate from assembly to C but it commonly made mistakes, some really hard to discover and fix.

Can you provide any examples for us interested?

And "system one".