Identity
Remote multiplexer
rmux_
Sess.DETACHtmux-01
Dir.LOCAL~/dev
rmux_
Remote multiplexerPersistent remote workspaces for AI agents
Close your laptop. Your agents keep coding.
RMUX gives each project a persistent remote terminal on a cloud VM. Run Claude Code, Codex, or your own tooling, disconnect whenever you want, and reattach to work that never stopped.
Why RMUX
Less babysitting. More useful agent time.
The value is not another layer of interface. The value is keeping useful work alive while you disconnect, switch tasks, or hand the repo to another agent.
Your agent keeps working after you disconnect.
Start on a remote VM, close your laptop, and come back to the same shell, scrollback, and running process.
Run multiple agents without collisions.
Each workspace gets its own git worktree so feature work, fixes, and review runs stay isolated.
Use your cloud or let RMUX host the control plane.
AWS, GCP, E2B, or managed infrastructure all share the same CLI and workspace model.
Workflow
Start once. Detach. Reconnect.
RMUX keeps the loop small: bind a directory, create the remote workspace, and fan out only when the work actually benefits from isolation.
Bind the project
Configure RMUX once in a repo and it remembers which remote environment belongs to that directory.
Start the workspace
rmux new provisions the machine, syncs your code into /workspace, and drops you into a persistent tmux session.
Detach and fan out
Create extra workspaces for parallel agents, then reattach later to work that is already in progress.
One repo, multiple live tracks.
Keep the main workspace grounded in the shared project root, then create extra worktrees for feature work, bug fixing, or review passes without stepping on each other.
Platforms
Same workflow. Different infrastructure.
RMUX is opinionated about the developer loop, not about where the machine has to run.
Use your own AWS account directly.
Configure from the AWS CLI and attach without managing SSH keys.
Keep the same flow on Compute Engine.
Project-aware setup, remote sync, and workspace attach stay consistent.
Skip cloud account setup entirely.
Start with an API key and get the same workspace model immediately.
Centralize policy and access for teams.
Run the workflow behind a shared control plane with API-key based access.
Get started
From install to a running remote agent in minutes.
Follow the quick start, create the workspace, and let the machine stay awake so you do not have to.