Trebuchet

Launch the session over the wall: same conversation, same working tree, running on a VM.

The far side runs it with native Claude Code — claude --bg --remote-control --resume <id> "TREBUCHET COMPLETE: …". That is a background session managed by the machine's Claude Code supervisor: no terminal has to stay open, it survives your SSH disconnect, and Remote Control makes it reachable from claude.ai/code, the Claude app, or a terminal on the VM. The trailing prompt is what makes it start working on arrival rather than sit idle. No Herdr, no extra multiplexer.

Nothing here is destroyed. The local transcript stays on disk and the local repo is untouched — trebuchet copies, it never moves — so a failed throw costs nothing but a stray workspace on the far side.

Two things have to travel: