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.
Tag
19 posts tagged.
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.
A month of running Cursor and Claude Code daily on the same Next.js project. What each one is actually for, where they bit me, the cost difference, and why I kept both instead of picking a winner.
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.
Running three to five AI coding agents at once with git worktrees for two weeks: the exact setup, honest merge and cost numbers, the failure mode nobody warns you about, and when parallel agents are the wrong call.
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.
Hour three of vibe coding is where the magic wears off and the work begins. The agent starts drifting from its own code, re-implementing helpers and calling renamed props. I stay productive by committing at every green moment, re-grounding the context against real files every 30 minutes, narrowing the agent's scope when it wanders, and starting a fresh session when the context gets poisoned. Flow is a tool, not the goal.