Anthropic

On July 24, Anthropic released Claude Opus 5. The line that jumped out of the announcement was: frontier intelligence of Claude Fable 5 at half the price. A lot of Chinese coverage translated this as “Opus 5 cuts prices in half.” That summary is half right and half wrong. Half right because Anthropic’s own marketing line is exactly that: “frontier intelligence of Claude Fable 5 at half the price.” Half wrong because Anthropic did not cut the token price. Opus 5 still lists at $5 per million input tokens and $25 per million output tokens, identical to Opus 4.8. Fast mode is still 2x the base price on the Claude Platform and through usage credits in Claude Code. ...

On July 4, a widely-circulated post by @AYi_AInotes highlighted a line buried in SpaceX’s revised IPO filings: SpaceX is supplying Anthropic with $1.25 billion of compute every month, under a contract running through May 2029, with either side able to terminate on 90 days notice. The same window saw reports that Anthropic has locked in 1.4 GW of data-center capacity in Australia, with $15 billion in build-out cost. Read these three together and the story is not “Anthropic bought more compute.” It is that AI compute has quietly moved from being a cloud resource you rent by the token, to a piece of industrial infrastructure you buy on multi-year fixed contracts. In industrial-age language this is called a power purchase agreement (PPA). In the AI era it is still the same shape: a customer locks in capacity at a fixed price, the supplier locks in cash flow to build. I am calling this “compute as power plant,” and that is the thesis of this post. ...

I need to start by correcting something I wrote on June 5. In Anthropic’s overnight triple move: building agents and containing them at the same time, I read Anthropic as a company running “two parallel lines” — a public “contain Claude” engineering program and a quieter recursive-self-improvement research track — and concluded that Anthropic was the safety-first operator, walking a “guardrails first, then capability” path. I had three pieces of evidence: an open-source vulnerability discovery framework, a recursive self-improvement research post, and the engineering article “How we contain Claude across products.” I read those three together and concluded Anthropic’s engineering culture was more credible than OpenAI’s. ...

On the afternoon of June 26 (U.S. Eastern), OpenAI published a preview post for GPT-5.6 Sol on its blog, and parked the system card at deploymentsafety.openai.com. The same day, the Washington Post reported that the U.S. government will decide which users get access to GPT-5.6. The same day, Reuters reported Anthropic is releasing Mythos only to “trusted partners.” Three events, less than 24 hours apart, each individually heavy. I am not going to write “AI regulation is here” — that ground was covered on June 14 in AI regulation just walked into the product. What I want to do today is zoom in much closer: what does GPT-5.6 Sol’s launch actually change, for a normal user, a normal builder, a normal product spec writer. ...

Yesterday (June 23) Anthropic published Introducing Claude Tag on the Newsroom. The post is short, but somewhere in the middle there’s a line I read twice: Today, 65% of our product team’s code is created by our internal version of Claude Tag. Sixty-five percent. Of the code Anthropic’s own product team writes, 65% is written by Claude Tag. The source matters here. This isn’t a customer case study. It’s Anthropic dogfooding the thing, then publishing the number. It’s the same release pattern they used for Claude Code Artifacts on June 18. Anthropic ships only after the workflow has been chewed on internally long enough to be embarrassing not to. ...

If you only read feature comparison tables, Codex and Claude Code differ in thirty places: model choice, browser support, rate limits, phone handoff. That is not what I want to write about today. Today I want to write about a 350-like tweet, and the two core maintainers standing next to it. The tweet that broke the silence Peter Yang (@petergyang) writes the Practical AI tutorials newsletter, 150K+ subscribers. At 3:32 AM UTC on June 20, he posted: ...

The most expensive thing about being an AI engineer is not the model calls. It’s the meetings about the model calls. On 2026-06-18, Anthropic pushed out Claude Code Artifacts, and the timing feels deliberate. The product story they tell is small: a developer kicks off an incident investigation in Claude Code, and the agent publishes a page as it works. By the time standup starts, the page has refreshed twice, and the team is staring at the same URL instead of asking someone to walk them through what the agent found. That pitch is the entire reason I wanted to look at this. ...

On the evening of June 12 (US Eastern), the Wall Street Journal dropped a scoop. By the next morning, three stories occupied the top of Hacker News, The Verge had its own follow-up, and Times of India had pinned down the causal chain. This is not another round of “AI labs versus the regulators” commentary. Three things happened inside a 48-hour window, and they each hit a different layer of the two leading American AI companies. ...

On June 12, 2026, at least five of the top 30 stories on Hacker News were about the same thing: #1 “Twenty One Zero-Days in FFmpeg” #5 “First iOS app to use technique that finds latest variants of spyware” #7 “AMD Stiffs Researcher $10k Bug Bounty” #15 “Show HN: Astra – Autonomous Pentest” #20 “I Think They [Anthropic] Are Lying to You” Add to that CloakBrowser and RuView on GitHub monthly charts, addyosmani/agent-skills on daily charts gaining 2,656 stars in a single day, and Astra Autonomous Pentest at #17 on Product Hunt monthly. Same day, three platforms, five overlapping signals. ...

Less than 24 hours after Claude Fable 5 dropped, a Show HN project called FablePool rocketed to the top of Hacker News.¹ As I write this, the post is at 348 points and 181 comments, and it’s still climbing. The actual product is interesting, but the more interesting story is what the comments are actually arguing about, and what it means when you put it next to a tweet from the same week. ...