Skip to main content
Once an environment exists, day-to-day RemoteMux usage comes down to workspace commands.
The current directory is the selector. Re-enter the same local directory before using workspace or env commands so RemoteMux can load the binding from .rmux/state.json.

Basics

Running Commands Remotely

Send commands to a workspace without opening an interactive terminal:

Named Workspaces

Create isolated workspaces for parallel work:
For git repos, named workspaces use remote git worktrees. For non-git directories, RemoteMux creates copied folders. main always uses the shared /workspace root. Remove a workspace when done:

Background Servers

Keep a dev server in its own workspace so main stays clean:
The server stays running even when you detach from all workspaces.

Logs

Secrets

Secrets are available as environment variables in all workspaces.

Ports

Code Sync

rmux workspace new main performs the initial seed. After that:
  • Use git to move code between local and remote (recommended).
  • Use rmux env sync to push the current local directory into the environment root.

Common Patterns

Resume after disconnect

Close your laptop, switch machines, or lose Wi-Fi. The tmux session survives:

Code review in isolation

Long test suites

Run the full suite remotely while you keep working locally:
Last modified on March 30, 2026