Claude Code

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. ...

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. ...

I almost tweeted the Fable 5 launch post yesterday afternoon. Karpathy called it a “major-version-bump-deserving step change forward.” Alex Albert, Boris Cherny, Thariq, Garry Tan — all in. The first two stories on Hacker News were Fable derivatives. The timeline was begging me to do it. Then I opened the GitHub monthly leaderboard. mattpocock/skills added 56k stars in a month and cracked the top five.¹ Leonxlnx/taste-skill (a skill that teaches your AI taste) and hardikpandya/stop-slop (a skill that removes AI tells from prose) hit the same monthly chart the same month.² ³ Not one of them has “Fable” in the name. None of them are riding the model hype. They all do the same thing: make what the AI writes faster to review. ...

I keep my phone in Do Not Disturb during work hours, but on the evening of June 9, 2026, the X feed pulled me back in. Not because of one announcement — Anthropic has announcements every week. What stopped me was that there were three, all within hours of each other, and they were aimed at three completely different layers of the stack. If you only saw the headlines, you’d think this was a release week. It wasn’t. It was a position. ...

The most-pinned agent tweet of the last few weeks is not a new model launch, and it is not a benchmark record. It is plain, but the more you chew on it, the more it sticks: “Here’s your monthly reminder that you shouldn’t be prompting coding agents anymore. You should be designing loops that prompt your agents.” — @steipete The author is Peter Steinberger, the creator of OpenClaw and one of the most active builders in the agent toolchain. He pins it on a monthly cadence. ...

I was up late scrolling X when Guillermo Rauch, the CEO of Vercel, dropped a short thread. No hedging. No build-up. Just a one-word verdict. YES-CODE. An entire category of software, “no-code”, was built under the presumption that code is expensive, difficult, and scarce. Coding agents have forever changed the equation. Code is now cheap, easy, and abundant. [1] Within 24 hours, the same conclusion came back from three people who don’t usually agree on anything. ...

If someone asks me how a normal person should understand Claude Code and other coding agents, I would not start with code. I would start with a much simpler picture: put a pile of PDFs, screenshots, spreadsheets, meeting notes, and transcript files into a folder, then ask the agent to read them, write scripts where needed, and produce an HTML report you can actually open and inspect. That does not sound like “programming.” ...

What caught my eye in Claude Code this time was not the fact that it shipped another command. It was that it finally started treating orchestration as something worth caring about. /workflows looks like a feature toggle on the surface, but it feels more like a boundary line. It moves agents from “helpers that answer questions” toward “execution units that run by rule.” The change is quiet. It is not flashy. But I think it matters. ...

The phrase “second brain” has been stretched almost to the point of meaninglessness. For years, plenty of products have claimed to be your second brain. Most of them ended up being nicer notebooks. You save articles, clip pages, write thoughts, tag ideas, connect notes, and then most of that material sits quietly in a folder. Sometimes you search it. Sometimes you rediscover something useful. Sometimes you just feel mildly guilty about how much you have collected and how little you have reused. ...