Your agents never stop coding.

Persistent remote terminals on cloud VMs for AI coding agents. Run Claude Code, Codex, or your own tooling — disconnect whenever you want, reattach to work that never stopped.

Get startedDocumentation
rmux — ~/myproject
$rmux env new
✓ Environment ready
us-east-1 · t3.xlarge · ubuntu 22.04
$rmux workspace new main --attach
✓ Synced ~/myproject → /workspace
✓ Workspace "main" created
$rmux workspace run "claude code review"
→ Running in workspace "main" (detached)
$rmux workspace ls
NAME STATUS UPTIME
main active 2h 14m
feature-auth active 45m
fix-tests idle 12m
$

Use your favourite CLI agent

Claude CodeCodex CLICursorOpenCode
//Core features

Less babysitting. More useful agent time.

$ rmux workspace attach main
✓ Reconnected to workspace "main"
Agent still running — 2h 14m uptime
Scrollback intact — 1,847 lines
Last output:
✓ All 47 tests passing
✓ PR #142 ready for review

Persistent runtime

Start a session on a remote VM, close your laptop, and come back to the same shell, scrollback, and running process. Your agent never notices you left.

$ rmux workspace ls
NAME STATUS BRANCH
main active main
feature-auth active feat/auth
fix-tests idle fix/tests
agent-review active review/pr-42

Parallel worktrees

Each workspace gets its own git worktree. Feature work, bug fixes, and review passes stay isolated — multiple agents work simultaneously without stepping on each other.

$ rmux configure --show
backend = "aws"
[aws]
region = "us-east-1"
authMode = "aws-cli"
Other backends:
○ gcp
○ e2b
○ managed

Flexible deployment

AWS, GCP, E2B, or fully managed — RemoteMux adapts to your infrastructure. Same CLI, same workspace model, regardless of where the machine runs.

//Use cases

One tool. Every workflow.

$ rmux workspace run "claude --dangerously-skip-permissions"
→ Running in workspace "main" (detached)
$ rmux workspace attach
✓ Reconnected — agent still active
Claude: Completed auth module refactoring.
✓ All 23 tests passing
✓ PR #142 ready for review

Remote agent sessions

Run AI coding agents on remote VMs that persist after you disconnect. Come back hours later to completed work — refactors, test suites, and PRs ready for review.

Learn more
//Benefits

Built for developers. Designed for agents.

Your cloud stays yours

BYOC keeps all code and compute in your own AWS or GCP accounts.

Instant reconnect

Reattach to running work in under a second. No cold starts.

Git-native isolation

Each workspace is a real git worktree — no symlinks or hacks.

Works with any agent

Claude Code, Codex, Cursor, OpenCode & more.

Zero configuration drift

Same environment every time you connect. Deterministic and reproducible.

Team-ready

Shared control plane with API-key access and centralized policy.

//How it works

Three steps. Then forget about it.

01

Configure the backend

Choose AWS, GCP, E2B, or managed for this repo. RemoteMux keeps the config with the project directory.

$ rmux configure
02

Create the environment

Provision the remote runtime and bind the current directory so future rmux commands target the right environment.

$ rmux env new
03

Bootstrap the main workspace

Sync the current checkout into /workspace, create main, and attach to the remote tmux session in one step.

$ rmux workspace new main --attach
//Platforms

Same workflow. Different infrastructure.

AWS BYOC
Free/your own compute

Run on your own AWS account. Configure from the CLI and attach without managing SSH keys.

Get started
  • EC2 instance management
  • IAM-based access
  • Any region
  • Your VPC, your rules
  • Full data sovereignty
Quickest setupE2B
Free/usage-based billing

Skip cloud account setup entirely. Get the same workspace model with just an API key.

Start with E2B
  • No cloud account needed
  • Instant provisioning
  • API-key access
  • Same CLI workflow
  • Fastest setup path
Managed
Available/hosted control plane

Use RemoteMux-operated sandboxes through the hosted control plane. Same workspace lifecycle, no cloud account required.

Use managed cloud
  • No cloud credentials required
  • RemoteMux-operated sandboxes
  • Organization/project scoping
  • API-key access
  • Same workspace workflow
//FAQ

Questions? Answers.

What exactly is RemoteMux?

RemoteMux is a CLI tool that turns local project directories into persistent remote workspaces. Each workspace runs in a tmux session on cloud infrastructure, so your AI coding agents can keep working even after you disconnect.

Which AI coding agents work with RemoteMux?

Any agent that runs in a terminal. Claude Code, OpenAI Codex CLI, Cursor, OpenCode & more — if it can run in a shell, it works in a RemoteMux workspace.

Do I need my own cloud account?

Not necessarily. You can use E2B for instant setup with just an API key, use the managed cloud through the hosted control plane, or bring your own AWS or GCP account for full control.

How does workspace isolation work?

Each workspace gets its own git worktree within the same repository clone. This means multiple agents can work on different branches simultaneously without file conflicts or merge issues.

Is my code secure?

With BYOC, your code never leaves your own cloud account. RemoteMux manages the workspace lifecycle but your data stays in infrastructure you control.

Can I use RemoteMux with a team?

Yes. Hosted backends already support organization and project scoping, API-key access, and shared control-plane workflows. Teams can also use shared AWS or GCP accounts with BYOC.

From install to a running agent in minutes.

Follow the quick start, configure the backend, and let the machine stay awake so you don't have to.

Open quick startBrowse docs