cuda-dev: getting started
Your personal dev box on the cuda-dev hosts: connect over SSH, work inside tmux, and run Claude. Here is the whole thing start to finish — then the same steps written out below.
What you get
Section titled “What you get”You get one container per host — cuda-dev-kvdb, cuda-dev2-kvdb, … — so you can
use whichever host’s GPU is free. You reach it over SSH from your laptop while on
the office network or the VPN.
1. Set up the key you were sent
Section titled “1. Set up the key you were sent”When the sync bot invited you, it created your boxes and sent you a Bitwarden Send link containing your private SSH key. Open that link, save the key, lock it down, and point ssh at it:
mkdir -p ~/.ssh# paste the key from your Bitwarden Send into ~/.ssh/cuda-dev-kvdbchmod 600 ~/.ssh/cuda-dev-kvdbAdd an entry per host to ~/.ssh/config:
Host cuda-dev2-kvdb HostName 192.168.2.206 User dev IdentityFile ~/.ssh/cuda-dev-kvdb IdentitiesOnly yes2. Connect
Section titled “2. Connect”ssh cuda-dev2-kvdb3. Work inside tmux
Section titled “3. Work inside tmux”tmux keeps your session running on the box even if your laptop sleeps or your
connection drops — start everything inside it:
tmux new -s work4. Run Claude — and pick your model
Section titled “4. Run Claude — and pick your model”claudeOn first run Claude asks to trust the folder — say yes. Then choose your model
with /model:
- Opus — most capable; use it for real development work.
- Default (Sonnet) — great for everyday tasks and lighter planning or analysis.
Then just talk to it:
❯ hi● Hi! How can I help you today?5. Disconnect and resume
Section titled “5. Disconnect and resume”Your session lives on the box, not on your laptop. Detach with Ctrl-b d, log out,
and your work keeps running. Reconnect later and pick up exactly where you left off:
ssh cuda-dev2-kvdbtmux attach -t work