Author
M. Patel writes DevMoment field notes on AI dev workflow, tested on real work rather than demos.
The standalone /output-style command is gone as of v2.1.91, so most guides are stale. Here is the current way to switch styles, which of the four built-ins earn their place, and the keep-coding-instructions flag that quietly breaks custom styles.
A config field log: the exact Claude Code statusline I run in 2026, the four fields that earn their place, the ones I deleted, and why the bar sometimes shows up empty.
GhostApproval showed my Claude Code approval box a fake filename while the write went to my SSH keys. Anthropic called it outside its threat model, so the fix was mine. Here is the field log: what the symlink flaw does, who patched, and the three setup changes that held.
I ran Claude Code dynamic workflows daily for two weeks on a real Next.js project. Where the parallel subagents earned the token bill, where they quietly wasted it, and the four-question test I run before I type ultracode.
Claude Code memory is three things, and auto memory quietly remembered a workaround I never asked it to keep. My exact keep/prune split, plus a three-question test for what earns a slot.
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.
