Add remote SSH sessions: remote projects, indexing/search/resume, IDE over SSH

[HAN-oQo]

Summary

Adds remote SSH session support to Switchboard. Today Switchboard is local-only — it reads ~/.claude/projects off the local disk and spawns terminals against local shells. This PR lets you run Claude Code (and shells) on remote hosts over SSH, with remote hosts + directories treated as first-class projects, their past sessions indexed & searchable, click-to-resume on the host, and (opt-in) the remote CLI's diffs/file-opens rendered in Switchboard's local side panel.

Delivered in three phases (each a self-contained commit); this single PR combines them.

Screenshots use redacted demo hosts (gpu-server, build-box, *.example.com); no real infrastructure is shown.

Phase 1 — Remote sessions & host management

Add Project gains a Local folder | Remote (SSH) choice. Pick a host, choose a remote directory, and it appears in the sidebar with an SSH badge; its + launches Claude/shell on that host. Connect verifies/authenticates in place (spinner → green; popup only when the host needs a password/passphrase or first-time host-key confirmation — never a raw terminal). A remote directory Browse mirrors the local folder picker. ~/.ssh/config hosts import automatically; you can also add hosts manually (identity file + extra -o options) and optionally write them back to ~/.ssh/config. Connections are multiplexed (ControlMaster) so you authenticate once per host.

Phase 2 — Indexing, search & resume

A connected host's past sessions are indexed (metadata over the existing SSH connection — no transcript copied to disk) so they persist in the sidebar, are searchable, and resume/fork in a terminal on the host. Auto-discovered by each session's cwd, grouped by remote directory, with the SSH badge + Claude logo + a ⟳ refresh. Full-text search covers remote transcripts; "View messages" streams a remote transcript live over SSH.

Phase 3 — IDE emulation over SSH

Opt-in: a remote Claude session pushes proposed diffs / file-opens into Switchboard's local side panel, exactly like a local session (review, accept, edit-then-accept, reject). It reverse-forwards the local IDE WebSocket port to the remote host (ssh -O forward -R), writes an IDE lock file there so the remote claude --ide connects back through the tunnel, and sources the diff's old side from the remote via ssh cat (the new side comes from the CLI). Off by default — the tunnel exposes the local IDE port on the remote host (protected by a per-session token), so it's enabled per your trust.

This phase also unifies the remote New Session popover and Configure dialog with the local ones (same labels/buttons; only justified differences remain — a Remote Directory picker, and Worktree/Chrome hidden as local-machine features; Pre-launch Command now applies to remote too).

How it works

• Transport: an SSH profile mirrors the existing WSL "wrapped command" pattern; the remote command runs in a login+interactive bash, single-quoted to survive ssh's argv re-join + remote-shell re-parse. One ControlMaster socket per host is reused by Browse, indexing, resume, and the IDE tunnel.
• Model A: a project is local or remote. Remote projects persist in settings; sessions group under a synthetic ssh://<host>/<dir> path.
• No local mirror: transcripts are read on demand over SSH (indexing metadata, View messages, and the diff's old side) — nothing is copied to local disk.
• Auth: interactive PTYs let the user answer password / passphrase / passkey / 2FA / host-key prompts; Switchboard never stores secrets.

Data / settings

• Additive migration adds a source column to session_cache + search_map (NULL = local; no cache wipe). All folder-scoped queries are source-isolated.
• New setting remoteIde (default off).

Testing

• Unit tests (npm test, run under Electron's node to match the app's better-sqlite3 ABI): SSH arg assembly + ~/.ssh/config parsing + quoting/transport (Phase 1); JSONL parsing, listing/framing/diff/cwd parsers, the source migration + isolation, sync orchestration, sidebar grouping (Phase 2); reverse-forward/cancel arg builders, the IDE lock script, the injected old-file reader (Phase 3). Full suite green.
• The v3→v4 migration was verified against a copy of a real DB (rows preserved, source backfilled to local).
• Manual: connect → launch/resume remote sessions; past sessions appear + are searchable + persist across restart; with the IDE setting on, a remote session's diff appears in the local panel with both sides populated, and accept-edited writes on the remote; no leftover remote lock on exit.

Roadmap

• Phase 1 — Remote sessions & host management: launch Claude/shell on remote hosts; hosts + directories as first-class projects; interactive Connect; remote Browse; host config.
• Phase 2 — Indexing, search & resume: past remote sessions indexed (metadata over SSH, no disk copy), searchable, persisted, and resumable/forkable on the host. Adds a source column.
• Phase 3 — IDE emulation over SSH: reverse-forward the IDE socket so remote proposed diffs / file opens land in the side panel (behind a setting); unify remote/local session UI.

(Remote Control — claude --remote-control for live cross-device mirroring — is orthogonal to local-vs-remote and is tracked separately, not part of this PR.)

🤖 Generated with Claude Code