Claude Code, meet Paddock
I don't know about you, but I have dozens of Claude Code sessions going at any one time. There will generally be a handful of them that I'm actively paying attention to, and then a long tail of chats that I want to keep around but might not need to look at for a while. But it's really hard to manage 50+ terminal tabs, and it's painful to restore all that state after a laptop restart.
And beyond that, I'm sick of being chained to my laptop. It's not natural. I want to be able to keep hundreds of Claude Code sessions going across any number of projects, and access them from anywhere, in a modern UI that doesn't hurt my middle-aged eyes. I need a Paddock to put my herd of Claudes in.
Paddock is a thin wrapper around Claude Code. As well as solving Claude Code terminal tab hell, it brings some powerful features that Claude Code really ought to have:
- Persistent sessions that survive restarts
- 1-click forking of sessions
- Chat sessions that can spawn child chat sessions, even between projects
- 2-way file sending with beautiful rendering of images, code, markdown and other types of content
- Triggers and schedules with per-session Claude Code configurations
It works with your Claude Max plan (and dear god will it drain that thing dry), and it frees Claude Code from the confines of a single machine. The best way to run it - the way I run it - is on a dedicated small server in your house. You can totally run it on your laptop if you want, but having Claude Code running on a 24/7 box that you can access from any laptop or phone is a game changer.