Two user-facing release channels exist for Claude Code. The default — what every npm install and every auto-update resolves to — is the bleeding-edge one, not the production-stable one. We checked the binary, ran the comparison against four peer CLIs, and wrote up how to opt in to stable.
“There’s a difference between AI helping you build the thing that expresses your judgment, and AI replacing the judgment itself.”
— from the studio notes, VSITS †
We've spent the past several weeks dissecting Claude Code's cache management bugs, building fixes, and documenting hidden costs. There's still one question we owe a clean answer to: what does
29 Apr 2026Update (April 24, 2026): Anthropic published a post-mortem on April 23 acknowledging three issues: a reasoning effort default change (March 4–April 7), a caching bug that continuously cleared thinking on
23 Apr 2026Previously in this series: How to Get a 99% Cache Hit Rate and Keeping Your Cache Warm with /coffee. Three things shipped in v2.1.117 that matter. One is a bug
22 Apr 2026In our cache investigation series, we documented how prompt cache bugs were causing 10-20x cost inflation on Max plans. We built a fetch interceptor to fix them. We thought we’d
21 Apr 2026Three ways to engage — from a one-week tooling audit to embedded engineering for teams running agents in production.