> ## 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.

# Introduction

> Persistent remote workspaces for AI coding agents.

RemoteMux turns the directory you are in into a persistent remote workspace. Work runs on a long-lived cloud environment with `tmux` sessions that survive disconnects, laptop sleeps, and Wi-Fi drops.

<CardGroup cols={2}>
  <Card icon="rocket" title="Quick Start" href="/quick-start">
    Launch your first environment and attach to a remote workspace.
  </Card>

  <Card icon="bot" title="Use AI Agents" href="/guides/ai-agents">
    Run Claude Code, Codex, or any CLI agent on a persistent remote VM.
  </Card>

  <Card icon="cloud" title="Choose a Backend" href="/concepts/backends">
    Compare AWS, GCP, E2B, and Managed backends.
  </Card>

  <Card icon="terminal" title="Troubleshooting" href="/troubleshooting">
    Fix failed checks, missing credentials, attach problems, and sync issues.
  </Card>
</CardGroup>

***

## Core Concepts

| Concept           | What it means                                                                                                                                                                     |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Directory binding | RemoteMux binds the current local directory to one remote environment in `.rmux/state.json`. Re-entering the same folder lets RemoteMux find the right environment automatically. |
| Environment       | The long-lived remote compute and `/workspace` for one project. `env down` stops compute without deleting state; `env destroy` removes it entirely.                               |
| Workspace         | An isolated checkout in the environment with a `tmux` session. You can keep `main`, `server`, and agent workspaces running in parallel without conflicts.                         |
| Backend           | The infrastructure provider (AWS, GCP, E2B, or Managed). The RemoteMux model stays the same across all backends.                                                                  |