Find an alternative.

1. I'm not sure if blacksmith offers larger runners, but you if you're using them you have checked that bigger runners are worth the squeeze? A 2x runner does not mean a 2x faster build - I had a goal and sized CI according to that.

2. Caching. Nx can do this for your TS, provided your code is decomposed into packages.

3. At a previous job I had a post-run timings job. GH markdown supports Mermaid; I used a gannt chart to express it. I don't remember if the GH api supports getting timing for the current wf - so it may have been a second workflow.

The first is just a little legwork, the rest your agent should be able to do in 5 minutes.

Where do you get this from?

Enterprise plans are being cancelled or limited all over the place (Uber, Microsoft). I doubt Anthropic would be leveraging a loss leader with their consumer plans, while catastrophically hemorrhaging customers on the enterprise.

They are either operating at a loss (possibly a minor one), or a minor profit (which is chasing customers away).

If they were comfortably profitable they wouldn't need to participate in the circular deal circus.

C and C++? You've got to be joking. If the project provides static binaries, sure, but I don't want to have to worry about finding a necronomicon and summoning the correct kind of imp required to properly use whatever insane build system the project is using.

I think we can make an educated guess as to why. Maybe we could get Claude to reverse engineer it to clean up its own mess.

[1]: https://www.cnbc.com/2026/05/18/s-korea-market-volatility-ne... [2]: https://www.fool.com/earnings/call-transcripts/2026/06/03/br...

Edit: oh, it's yours. Spend 5 minutes understanding exactly what SKG have said they are not asking for.

It looks like this is left as an exercise for the student?

> Gooey is in better shape than most ~140 KLOC Zig codebases — every directory has a mod.zig, namespaces are layered, and core/interface_verify.zig provides compile-time platform-backend checks. But the architecture has drifted in a few

I too have used AI to plan cleaning up its own mess, and this self-congratulatory prose is extremely consistent ("every directory has a mod.zig", whoop dee woo!).

In my experience, AI is largely incapable of fixing its own mess to an actually competent degree (and full disclosure: I still ask it to, not pointing fingers here) and it's probably due to it walking on egg shells around its own feelings. I've had to tell it to completely change course during cleanup at least 30 times this week.

Also: https://xcancel.com/mitchellh/status/2060088112257372610

Though this is largely impossible these days, unless they pre-trained on pre-AI era data.

That being said, there's still a chance that NVIDIA engineering is in the process of stripping it for parts. Or the lawyers are - maybe they have too much momentum with GPUs and just want ASICs out of the market.

This kind of innovation stifling acquisition should have been blocked. NVIDIA is a serious monopoly threat.

Feeling consequences are how they are kept in line. Maybe next time they will think twice before (allegedly) treating a person like they did here, as well as the creative reasoning I recall them using in the past to reduce payouts.

* Ralph Wiggum loops

* Simply not allowing an agent to stop its turn until all tasks are marked as done

* Sub agents over worktrees

* Context compression

It is widely suspected that self-inflicted "bad news" ("Mythos is so dangerous we just can't give the public access to it") is nothing more than Dario's typical style of marketing - keep in mind that they have an IPO coming up, because he certainly factors that into everything he says in public (as is his responsibility, to be fair).

An alternative reason for delaying the model might not be "we are trying to make it safe." It could be "we don't know how to host this thing at scale, or cost-effectively".

GPT 5.5 has already been shown to be as adept as Mythos at finding vulnerabilities.

Finally, laymen massively underestimate the importance of the harness for model performance. OpenHands existed long before Claude Code, Claude Code changed everything because of the clever hand-holding it does. Mythos is definitely more than just a model.

We've also increased how much our coworkers need to read, or deal with. You can get an AI to make any point you want, so you can ignore the 5 humans raising alarms due to the 1 clanker you made say what you want to hear.

All numbers going up.

There are obviously people producing additional true value with it, probably, but that's almost certainly scarce.

[1]: https://en.wikipedia.org/wiki/Perverse_incentive