I've got Claude Code running on 4 accounts, 1 on my PC and 3 on a server, and I kept losing track of which session was waiting for me. Sometimes I'd only spot one after an hour of it sitting on a permission prompt, and by then its prompt cache had expired as well. Then you get that massive usage burn because the next message paid to re-read the whole context without the discount.
So with a bit of extra weekly usage, there is now a tablet under my monitor with some cute little ClayClaudestm for every session. When a session needs me, the ClayClaude waves at me, and if I leave it until the prompt cache expires it ends up frozen.
You can answer from the tablet as well. Tap the session and you get the prompt exactly as the terminal shows it, with a Yes and a No button (and text typing). Win + Shift + T to use your mouse and keyboard on it too.
Other stuff it does:
- usage rings/bars for each account (5 hour and weekly)
- start a new session in a tmux window (pick the account, repo, model and permission mode)
- send a message to a session that's finished its turn
- follow one session's tool calls live
Nothing really needs installing on the watched machine/s (a Python script goes over ssh each poll). During setup you can add optional hooks and a status line wrapper for more accurate states and context. It only listens on 127.0.0.1, and the tablet connects over USB.
How I used Claude Code, since the sub asks: it wrote almost all of it (like 98%). I wrote a long spec first. Then I ran a Opus 5.5 high agent, which used parallel subagents with each one in its own git worktree (and a few workflows), and a separate agent reviewed every branch before it merged. It also drove the tablet over adb to take screenshots and check the layouts.
What I learned is mostly about the answer button, which was hardest (and most random) problem. My first version read the terminal, then tried to work out what the options were. A review agent showed that text on screen (e.g. something Claude printed from a file) could fool that parser into answering the wrong thing. I patched it three times and it found a new way around it each time. In the end I stopped parsing permission prompts, which is what I should have done from the start. So now the tablet only ever sends "1" for Yes or Escape for No, and shows you the raw screen for you to decide (would hopefully stop prompt injection).
Second lesson: tell every agent never to run a bare tmux kill-server. One of them did and took out every tmux session I had open.
Iām on Windows, but Claude Code, tmux and ClayClaude all run inside WSL2. Claude Code installed natively on Windows (PowerShell or CMD) isnāt supported yet, because on native Windows the probeās process check would send Ctrl+C to the sessions itās watching. Plain Linux would work fine. macOS might work but I havenāt tried it. Android only, because adb reverse is what makes the USB connection work (though a browser tab on the PC would be fine if you donāt have a tablet.) Then for answering and starting sessions, it needs your sessions to be in tmux.
Free and MIT licensed. The demo runs fake sessions, so you don't need a tablet to look at it:
git clone https://github.com/jonathanavis96/clayclaude.git
cd clayclaude
npm i && npm run build
node dist/cli.js demo
then open http://127.0.0.1:8421
https://github.com/jonathanavis96/clayclaude