Intermediate7 min
SSH Remote Development and Cross-Machine Workflows
Running Claude Code on a remote server over SSH gives you access to powerful hardware, production-adjacent environments, and shared dev boxes — with full Claude Code capability. VS Code Remote SSH adds the full IDE experience on top.
Quick Reference
- →SSH Claude Code: install on the remote machine, connect via SSH, full CLI available
- →VS Code Remote SSH + Claude Code extension: full IDE + inline diffs on the remote machine
- →Repo must be on the remote machine — Claude Code operates on local files
- →Port forwarding: forward dev server ports to see live preview locally
- →Remote MCP servers: team-shared MCP tools accessible from any Claude Code session
- →Superset.sh: open-source orchestration layer for 10+ parallel agents in isolated worktrees
- →When remote makes sense: GPU servers, production-adjacent environments, shared dev boxes
When Remote Development Makes Sense
Running Claude Code on a remote machine is the right call in several situations:
- ▸GPU or high-memory servers: running Claude Code on a server with more RAM or GPU lets Claude index and analyze larger codebases without local resource constraints
- ▸Production-adjacent environments: develop against a staging DB, real services, and production-like config without replicating everything locally
- ▸Shared dev boxes: teams with shared development machines can run Claude Code on the shared machine without each developer installing locally
- ▸Resource-intensive operations: large codebase analysis, full build pipelines, memory-heavy test suites