Claude Code's Monitor Tool vs Polling: What Actually Happened
I gave Opus 5.5 a build to watch and a dev server to start, with and without the Monitor tool. It used Monitor inconsistently, and headless runs hid the answer.
7 articles
I gave Opus 5.5 a build to watch and a dev server to start, with and without the Monitor tool. It used Monitor inconsistently, and headless runs hid the answer.
ultrathink now runs at xhigh effort in Claude Code. I ran six exact-answer tasks 96 times from low to max: every level got them right; higher just cost more.
I had Haiku 5.5 audit 30 of my posts twice: once with --json-schema, once asking nicely for JSON. The shape held. The judgement moved, and that's the lesson.
I hid five bugs in a real change and ran /code-review at low, medium, high and xhigh. Medium found all five for 15 cents. Here's what each level adds.
Slides is out of beta. I had Claude Code turn one of my posts into a nine-slide deck, then checked every claim against the source. Here's what held up.
A Claude Code mod to hold destructive Azure CLI commands passed 12 unit tests and stopped nothing live. Here's why, the fix, and the gap no regex closes.
I gave Haiku 5.5 and Opus 5.5 the same five chores in this blog's repo. Both passed every run. Haiku cost 25 times less, and the diffs show what Opus adds.