Skip to main content
These are the patterns RMUX users reach for most often. Each one starts from a project directory that already has an environment (rmux new has been run at least once).

​
Overnight Agent Runs

Start a large refactoring or migration task, go to sleep, check results in the morning. 
cd my-project
rmux workspace attach

# Inside the remote terminal, give the agent a big task:
claude

# Once the agent is working, detach:
# Ctrl+B, then D

# Close your laptop and go to sleep.
The next morning: 
cd my-project
rmux workspace attach
# Full scrollback shows everything the agent did overnight.
Use rmux env down when you are done to stop compute costs. The workspace state is preserved — run rmux new in the same directory to resume later.

​
Parallel Feature Development

Run multiple agents on different features at the same time. Each workspace gets its own git worktree, so agents do not create merge conflicts. 
# Create isolated workspaces
rmux workspace new feature-auth
rmux workspace new feature-payments
rmux workspace new fix-ci

# Start an agent in each one
rmux workspace attach feature-auth
# Start Claude Code, give it the auth task, detach

rmux workspace attach feature-payments
# Start another Claude instance, detach

rmux workspace attach fix-ci
# Start Codex for CI fixes, detach
Check progress across all workspaces: 
rmux workspace ls
rmux workspace logs feature-auth --follow
rmux workspace logs feature-payments --follow
When agents finish, their branches live in their worktrees. Attach to review, then use git to push, fetch, and merge them locally or from main.

​
Long Test Suites

Run your full test suite on the remote VM while you keep working locally. 
# Send the test command without attaching
rmux workspace run bun test

# Or create a dedicated workspace for it
rmux workspace new tests
rmux workspace run -w tests bun test -- --coverage
Check results later: 
rmux workspace logs tests --follow

​
Background Dev Server

Keep a dev server running in its own workspace so your main workspace stays clean for interactive work. 
rmux workspace new server
rmux workspace run -w server bun run dev

# Expose the port for external access
rmux env expose 3000
rmux env ports
The server stays running even when you detach from all other workspaces.

​
Resume After Travel

Start work at the office, close your laptop, reconnect from home (or your phone, or a different machine). 
# At the office:
cd my-project
rmux workspace attach
# Work, then close your laptop and leave.

# At home, on a different machine:
cd my-project
rmux workspace attach
# Same session, same scrollback, same running processes.
RMUX stores the project-to-environment binding in .rmux/state.json inside the project directory. As long as you are in the same local directory, RMUX finds the right remote environment.

​
Code Review In An Isolated Workspace

Review a PR without touching your main workspace: 
rmux workspace new review-pr-42

rmux workspace attach review-pr-42
# Inside: git fetch && git checkout pr-branch
# Run the app, inspect the code, then detach

# Clean up when done
rmux workspace rm review-pr-42

​
Inject Secrets For Agent Use

Agents often need API keys. Set them once per environment and they are available in every workspace: 
rmux env secrets set ANTHROPIC_API_KEY sk-ant-...
rmux env secrets set OPENAI_API_KEY sk-...
rmux env secrets ls

​
Editor Access

Open a workspace in VS Code or Cursor without attaching to the terminal: 
rmux workspace code main
rmux workspace cursor server
rmux workspace editor main --vscode
This works on aws and gcp backends where RMUX can set up an SSH connection for the editor.

Running AI Agents

Detailed agent setup for Claude Code and Codex.

Day-To-Day Commands

The core workspace commands in one place.

Environment Lifecycle

Create, stop, resume, and destroy environments.

Troubleshooting

Fix attach, sync, and binding problems.
Last modified on March 24, 2026