Editor Access - RemoteMux Docs

RemoteMux can open workspaces directly in VS Code or Cursor without using rmux workspace attach.

Commands

rmux workspace code main            # open in VS Code
rmux workspace cursor server        # open in Cursor
rmux workspace editor main --vscode # explicit editor flag

These open the workspace path in the editor. They do not attach to the workspace’s tmux terminal.

Backend Support

Backend	Supported	Transport
`aws`	Yes	SSM-backed SSH tunnel
`gcp`	Yes	`gcloud`-managed SSH key plus an IAP-backed SSH proxy
`e2b`	No	E2B uses the PTY API, not SSH
`managed`	No	Use `rmux workspace attach` instead

What RemoteMux Changes Locally

On first editor open, RemoteMux:

Seeds or refreshes the local GCP SSH key with gcloud compute config-ssh when backend=gcp
Writes RemoteMux-managed host entries under ~/.ssh/rmux/config
Ensures ~/.ssh/config includes Include ~/.ssh/rmux/config
Creates an editor-specific SSH host alias for the target workspace

For backend=gcp, the generated alias proxies SSH through gcloud compute start-iap-tunnel instead of dialing the VM’s public IP directly.

AWS Auth Mode Behavior

Auth mode	`rmux workspace editor`	Standalone `ssh rmux-...`
`aws-cli`	Works	Works (via configured profile)
`env`	Works (RemoteMux injects credentials)	Requires ambient AWS credentials
`access-key`	Works (RemoteMux injects credentials)	Requires ambient AWS credentials

Last modified on April 2, 2026