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

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

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-kvdb
chmod 600 ~/.ssh/cuda-dev-kvdb

Add an entry per host to ~/.ssh/config:

Host cuda-dev2-kvdb
  HostName 192.168.2.206
  User dev
  IdentityFile ~/.ssh/cuda-dev-kvdb
  IdentitiesOnly yes

2. Connect

ssh cuda-dev2-kvdb

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 work

4. Run Claude — and pick your model

claude

On 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

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-kvdb
tmux attach -t work

6. Recover AI sessions after a box restart

A host or container restart also stops tmux. The cuda-dev setup records open Claude Code and Codex sessions so you can resume them afterward. Reconnect and preview the sessions that can be recovered:

restore_ai_sessions.sh --list

Restore them into the detached ai-restore tmux session, then attach:

restore_ai_sessions.sh
tmux attach -t ai-restore

If you run the restore command from inside another tmux session, switch to the recovered session instead:

tmux switch-client -t ai-restore

Each recovered Claude Code or Codex session opens in its own tmux window. A normally closed AI session is removed from the recovery list. Codex asks you to trust the installed session hook once; open /hooks in Codex and approve register_ai_session.sh when prompted.