Part 2: From cct to cad — when a personal fork stops being a fork

Part 2: From cct to cad — when a personal fork stops being a fork

Last time I wrote about forking Simon Willison’s claude-code-transcripts to fix some personal pain points — folder-grouped picker, Global Sessions, the night I deleted 1,628 runaway loop sessions, an iMessage-style dark theme. I closed with “there’s a particular kind of joy in not asking permission” and figured I’d be done.

I was not done.

The thing that broke the “personal fork” framing for me was a slow realization: the workflow I was fixing wasn’t claude-specific. I use Claude Code 90% of the time, but the rest of my AI coding life happens in codex, pi, opencode, and forge. Each of those CLIs stores sessions somewhere. Each has its own resume command. Each one is a tiny half-tool with a session list inside it. There’s no overlap between any of them.