Give Claude Code A Voice
On this page
- An agent run has exactly two interesting moments
- What the two sounds actually say
- Why sound, and not a desktop notification
- Where the two sounds hook in
- The shape that trips everyone up
- Narrowing the notification
- Four details that will bite you
- What else is tempting, and why I stopped
- Making your own
- What it actually changes
Related Articles
The ABCDE Of Agent-Driven Development
A five-skill todo lifecycle for Claude Code — Add, Brainstorm, Code, Deliver, Explore — that carries a one-line idea to a reviewed, merged PR without letting a fire-and-forget agent make silent choices. A full tour of every stage and every pillar underneath.
Give Claude Code A Visual Language
Turning a client-rendered app into a server-rendered one is not a pull request. It is six of them, in an order that matters, over three weeks — and by the second week nobody can answer "where are we?" without twenty minutes of scroll-back. Here is the shape that fixed it — one outline artifact, one step per pull request, and a link that points both ways.
What Is An Agent Harness? The Pattern Behind Every AI Coder
A deep dive into agent harnesses — the loop that wraps an LLM and turns it into something that can read files, run tests, and ship code. We break down the six parts, the turn loop, the design tensions, and build one in 30 lines of TypeScript.
Why You Should Know About MCP Apps And When To Use Them
AI assistants can now show a real, clickable interface from someone else's product right inside the conversation — a chart you can drag, a form you can fill in, a preview you can approve. That is MCP Apps, the open standard for putting a product's own UI inside Claude, ChatGPT and a growing list of other AI hosts. This is how it works, why it matters if you ship software, and the handful of situations where it is the right tool rather than a gimmick.