Workflow

TL;DR: After 165 sessions with Claude Code and 27 with Codex CLI, one thing is clear: use Claude for interactive, exploratory work and Codex for autonomous tasks you can delegate and forget about. It’s not about which is better — it’s about when to use each. My data shows the combination outperforms either one alone. It’s 9:00 a.m., coffee in hand, and I have a vague idea about restructuring a module. I don’t know exactly what I want yet — I just know the current setup isn’t right. ...

I currently have three Claude Code sessions open. One is translating blog posts. Another is writing tests for a CLI. The third is helping me debug a data pipeline. Each one runs in its own worktree, each one in its own Ghostty split, while I jump between them using Cmd+Alt+Arrow. I haven’t opened iTerm2 in months. I haven’t touched tmux in weeks. Everything lives in a single Ghostty window. Is it the perfect setup? No. Is it the most productive setup I’ve ever had? Absolutely. ...

A few weeks ago, I wrote about git worktrees — what they are, how to create them, and why they’re better than cloning a repo three times. The basics. But the basics are only half the story. Because Claude Code doesn’t just work with worktrees — it has native support for them. Dedicated flags, automatic isolation, integration with tmux. And the difference between knowing worktrees exist and knowing how Claude Code uses them is like the difference between having a car and knowing it has sport mode. ...

The Single Checkout Bottleneck I’m developing a macOS menu bar app. I have three features in the backlog: a consumption sparkline, native notifications, and a desktop widget. All three are independent. I’m building all three with Claude Code. The problem: Claude Code works in one directory. One directory has one branch. And git checkout is like a single-lane roundabout: only one gets through. If I want to advance all three simultaneously, my classic options are: ...