> ## Documentation Index
> Fetch the complete documentation index at: https://docs.remotemux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspaces

> How RemoteMux uses tmux-backed workspaces for parallel work.

Workspaces are the units you work in once an environment exists.

## The Default Workspace

Every environment starts with a workspace named `main`:

* `main` uses the shared `/workspace` root
* It has a primary `tmux` session
* `rmux workspace attach` targets it by default

## Named Workspaces

Named workspaces let you keep parallel work isolated:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
rmux workspace new server
rmux workspace new agent-a
rmux workspace new agent-b
```

For git repos, named workspaces use remote git worktrees. For non-git directories, RemoteMux creates copied folders.

## Commands

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
rmux workspace attach            # open the default workspace
rmux workspace attach server     # open a named workspace
rmux workspace run bun test      # send a command without attaching
rmux workspace logs server       # view workspace output
rmux workspace rm agent-a        # remove a workspace
```

## Editor Access

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
rmux workspace code main         # open in VS Code
rmux workspace cursor server     # open in Cursor
```

Editor access currently supports `backend=aws` and `backend=gcp`. See [Editor Access](/guides/editors) for details.