Anthropic

The first time I used Claude Code to refactor an entire module, it felt almost mystical. I described what I wanted, went to grab a coffee, and when I came back, there was a pull request with 14 files changed, updated tests, and a decent commit message. “This is magic,” I thought. It’s not magic. It’s a while loop. Michael Bolin from OpenAI recently published an article dissecting the internals of Codex CLI. And it turns out that the secret behind AI coding agents isn’t a groundbreaking algorithm or an enigmatic neural network. It’s a loop that calls an LLM, executes tools, and repeats until there’s nothing left to do. ...

A few weeks ago, I published an article explaining why 99% of what you send to Claude is already cached. KV tensors, VRAM, local SSDs — the full internal machinery. But I left out the part that hurts the most: the bill. Because prompt caching seems like a sweet deal until you look closely at the numbers. And then you realize that you’re paying to save. The cost paradox Let’s crunch the numbers. With Claude Sonnet: ...

For months, I’ve been running Claude Code tasks using a homemade cron. A Bash script that starts a headless session, feeds it a prompt, waits for it to finish, and then closes. It works. Barely, but it works. I’ve got it up on GitHub if anyone’s interested. Then on Friday, with version 2.1.71, Anthropic introduced /loop. A native scheduler. Built directly into Claude Code sessions. My first reaction was: “They killed my project.” ...

I’m building Tokamak, a menu bar app for macOS that monitors your Claude Max quota. A couple of weeks ago, Anthropic published this in their Terms of Service: “You may not use OAuth or similar authorization mechanisms to allow third-party applications to access Claude on behalf of users.” And there I was, reading Claude Max quota using browser cookies to call an undocumented endpoint, staring at the screen thinking: “What now?” ...

I’m building an app that monitors my token consumption in Claude Code. A few days ago, looking at the raw numbers, I found this: cacheReadInputTokens: 4,241,579,174 inputTokens: 1,293,019 Four billion two hundred million tokens read from cache. One million three hundred thousand “fresh” tokens. That’s a 99.97% cache hit rate. My first reaction was to think something was broken. Nobody has 99% cache hit. Not Redis. Not Cloudflare. Not your mom when she tells you she already knows what you’re going to ask for lunch. ...

A 100-Megabyte Binary for a CLI Anthropic just announced that Claude Code is now available as a native build. Translation: a binary executable you can install with a curl command that doesn’t need Node.js. Sounds good, right? One command, no dependencies, background auto-updates. Any CLI tool’s dream. But there’s a catch: the binary weighs 100MB. To put this in perspective, the git binary weighs about 3MB. curl is less than 1MB. Even Go, which has a reputation for generating fat binaries, rarely exceeds 15-20MB. ...

The 10 GB surprise You install Claude Desktop on your Mac. Everything’s fine, the app is lightweight. But one day you check your disk and discover this: ~/Library/Application Support/Claude/vm_bundles/claudevm.bundle 10.8 GB. Excuse me? Ten gigs for a chatbot? What’s in there, the extended Lord of the Rings trilogy? Nope. It’s Ubuntu. The Claude product trinity Before I explain the what, let me explain the why. Anthropic has three ways to give you access to Claude: ...

The news nobody saw coming Last week, while you and I were peacefully wrestling with node_modules, Anthropic dropped a bomb: they’ve bought Bun. Yes, the company behind Claude has decided that their future depends on a JavaScript runtime written in Zig by a guy who thought “what if Node, but fast?”. Claude Code just hit one billion dollars in revenue, and apparently the first thing you do when you have money to burn is buy development tools. ...