Claude Code hooks: the 4 I kept, the 2 I deleted (2026)
I ran Claude Code hooks daily for a month. Four earned their place, two got deleted, and one quietly made my workflow worse. The honest field log.
Author
Backend dev. Writes when something breaks. Currently shipping a B2B agent product with one cofounder.
I ran Claude Code hooks daily for a month. Four earned their place, two got deleted, and one quietly made my workflow worse. The honest field log.
An AGENTS.md file helps AI coding agents, but only when it is short. A two-week field log on trimming mine from 412 lines to 38, and why less context beat more.
Reviewing AI-generated code is the new bottleneck. Here is the 15-minute triage system I run on every agent pull request, and when I just rewrite instead.
A short, honest June 2026 retro on what got cut from a working Claude Code config: the custom statusline, the over-engineered MCP wrapper, the autosave permission. Plus the one thing I almost killed and why I kept it.
Seven Claude Code subagents written in a week. Four still run daily, three are in the trash. The YAML, the tool whitelists, the cost-per-invocation numbers, the three anti-patterns I won't repeat, and the honest carve-outs where subagents are the wrong tool.
After a year of AI pair programming, I optimize my editor for reviewing, not writing. I format only modified ranges to keep diffs honest, switch to inline diffs, bind word-by-word accept and next-hunk navigation to fast keys, keep a short instructions file in version control, auto-approve only safe local commands, and commit constantly. The settings all follow one shift: I read far more code than I write now.