The Claude Code Statusline I Actually Read (and the Fields I Deleted)
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.
Category
16 posts in this category.
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.
A field note on Claude Code plan mode after months of daily use: when it saves me, when I skip it, three failure modes the listicles miss, and the exact habit I built around it.
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.
Six AI coding agents sit in my dock in 2026, but I do not open all six every day. Here is the honest field log of which one I reach for when the task is a refactor, a chore, or a tight edit loop, plus the routing rule that keeps surviving.
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.
A field note on Claude Code commands: which custom slash commands actually earned their place, which I deleted, and the 2026 question the listicles skip, when a command should have been a skill.
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.
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.