trident

a pretty common workflow for me when developing with claude code is the following;

1. setup claude code running on my local windows machine

2. ssh into my cluster and run claude code there

3. prototype ui on my local machine with mock data

4. setup backend that uses my gpus on my remote machine with some amount of handoff instruction after a git pull from the shared repo

this is fine, but I really want to be able to just spin up one session locally that spawns a cc session on the remote and for them to just talk to each other as needed. I can always pull up the claude code session on the claude webui as needed.

trident is my solution for that.

it uses claude's channels to communicate with each other and has some other quality of life things baked in like remote session launching.

funnily, the remote session while testing actually started to refuse to answer on like the 4th request citing it was getting spammed with nothing burgers for todo work.