Skip to main content
In RMUX, a project starts with the local directory you are standing in.

​
The Current Directory Is The Selector

RMUX is directory-first. When you run rmux new, RMUX stores a local binding for that directory. Later, re-entering the same folder lets RMUX find the right environment automatically. That is why many “not found” problems are really directory mismatch problems.

​
What Lives Locally

PathWhat it stores
./rmux.confProject-level RMUX config for this directory.
./.rmux/state.jsonThe local binding to the remote environment.
your source treeThe local code RMUX syncs into the remote environment.

​
The Binding Model

  • one project directory maps to one RMUX environment binding
  • RMUX loads that binding from .rmux/state.json
  • rmux workspace attach and rmux env status work because the directory tells RMUX which environment to target
If you need to act on an environment from another directory, use rmux env list first and target it by exact name or ID.

​
The Commands Tied To The Project Directory

rmux configure
rmux configure --show
rmux new
rmux workspace attach
  • rmux configure writes project config by default.
  • rmux configure --show prints the resolved config for the current directory.
  • rmux new creates the bound environment for that directory.
  • rmux workspace attach reconnects using the saved local binding.

Environments

Learn what the remote environment actually is.

Configuration

Go deeper on precedence, config files, and environment variables.
Last modified on March 21, 2026