Skip to main content
An environment is the long-lived remote runtime for one project directory.

​
What An Environment Contains

PartMeaning
remote runtimeThe VM or sandbox RMUX provisions for the project.
remote root/workspace, the main shared project root.
workspace setThe default main workspace plus any named workspaces you create.
lifecycle stateprovisioning, ready, stopped, destroying, or error.

​
One Environment Per Project Directory

When you run rmux new, RMUX:
  1. creates the environment
  2. seeds /workspace from the current local state or the repo’s origin default branch
  3. creates the default main workspace
  4. attaches to it unless you pass --no-attach

​
Environment Commands

rmux new
rmux env status
rmux env down
rmux env destroy
  • rmux env status shows provider, runtime details, last sync time, and workspace information.
  • rmux env down stops compute but preserves environment state.
  • rmux env destroy removes the environment entirely.
After creation, RMUX does not keep local and remote files in sync. Use git for ongoing code movement.

​
Other Things Stored At The Environment Level

  • secrets from rmux env secrets ...
  • exposed ports from rmux env expose ...
  • environment IDs shown by rmux env list and rmux usage

Workspaces

See how work is split inside an environment.

Environment Lifecycle

See the full command-level lifecycle guide.
Last modified on March 24, 2026