Claude Code shipped a virtual pet Easter egg. Two accounts, two penguins — the second one downgraded from Rare to Common. So I used Claude to brute-force a Shiny Legendary Dragon in 0.2 seconds.

The most novel thing in the Claude Code snapshot isn't a tool or a prompt. It's how aggressively the runtime is built around preserving prompt-cache identity across forks, compaction, and long-running sessions.

The most important file in the Claude Code snapshot isn't a prompt file or a tool definition. It's a state machine. Once you see that, a lot of agent design decisions start making sense.

After auditing a publicly posted Claude Code source snapshot and reading OpenAI's harness essays, I came away with one conclusion: the model is only the brain. The product is the runtime around it.

From discovering pretext to shipping 7 interactive effects across two sites in one session — explosion physics, bouncing bullets, and an animated crab named Clawd.

A 15KB JavaScript library just solved one of the oldest architectural debts in web development — knowing how tall text will be without asking the browser to reflow the entire page.

I wanted a voice-to-notes pipeline. The internet said build a watchOS app. A friend who tried said don't. Thirty minutes later — with Claude Code doing the heavy lifting — I had a zero-cost, zero-dependency solution using nothing but Voice Memos, iCloud, and one Gemini API call.

First principles on AI: every trend, traced to its root, is about whether there's enough compute — and whether it's good enough

How I built a hybrid read+write WeChat automation pipeline on macOS — the tools, the architecture, and the 6 pitfalls that'll save you hours

Three demand curves, one deflation trend, and why compute is the new oil