Skip to main content
RMUX can open supported workspaces directly in VS Code or Cursor without using rmux workspace attach.

​
Commands

rmux workspace editor main --vscode
rmux workspace editor agent-a --cursor
rmux workspace code main
rmux workspace cursor agent-a
These commands open the workspace path in the editor. They do not attach to the workspace’s tmux terminal.

​
Backend Support

BackendSupportNotes
awsYesUses an SSM-backed SSH tunnel.
gcpYesUses gcloud compute config-ssh details.
e2bNoThe current editor flow is SSH-based, but E2B attach uses the PTY API.
managedNoUse rmux workspace attach for interactive access.

​
What RMUX Changes Locally

The first editor open:
  • writes RMUX-managed host entries under ~/.ssh/rmux/config
  • ensures ~/.ssh/config includes Include ~/.ssh/rmux/config
  • prepares an editor-specific SSH host alias for the target workspace

​
AWS Details

For backend=aws, RMUX:
  • installs or reuses an RMUX-managed SSH key under ~/.ssh/rmux/
  • enables SSH access on the devbox through SSM
  • tunnels SSH with AWS-StartSSHSession
The devbox does not need an inbound port 22 rule. Authentication depends on aws.authMode:
  • aws-cli works for both rmux workspace editor and standalone ssh rmux-...
  • env and access-key work with rmux workspace editor because RMUX injects the resolved credentials into the launched editor process
  • standalone ssh rmux-... with env or access-key still depends on ambient AWS credentials in your shell

​
GCP Details

For backend=gcp, RMUX derives SSH host details from gcloud compute config-ssh, writes an RMUX-managed alias under ~/.ssh/rmux/config, and launches the editor against that alias.
Last modified on March 21, 2026