Cloud sessions
Run agent sessions in a managed cloud sandbox and pick them up from the IDE, CLI or Web.
A cloud session runs the Mind agent harness in a managed cloud sandbox instead of on your machine. The session belongs to your Mind account, not to any one app: start it in the browser, hand it a long task, close your laptop, and check on it later from your phone, your terminal, or the IDE. The agent keeps working in the sandbox whether or not you're connected.
Cloud sessions are the execution environment behind Mind Web, and the IDE and CLI can create and attach to the same sessions. Because every surface talks to the same harness through the same protocol, a cloud session behaves like any other Mind session: same steering, same permissions, same tools.
| Capability | IDE | CLI | Web |
|---|---|---|---|
| Create a cloud session | ✓ | ✓ | ✓ |
| Resume and steer an existing cloud session | ✓ | ✓ | ✓ |
| Autonomous mode | ✓ | ✓ | ✓ |
| Scheduled automations | — | — | ✓ |
How cloud sessions work
When you create a cloud session, Mind provisions an isolated sandbox and starts the same agent harness that runs locally in the IDE and CLI. If you attach repositories, Mind clones them server-side through your connected source provider; your local working copy is never uploaded. The agent reads, edits, builds, and runs shell commands inside the sandbox, and delivers results back through your source provider (typically as a pull request) or directly in the conversation.
The session itself lives in a cloud session store, separate from any client:
- Clients attach and detach: the Web app, IDE and CLI are all views onto the same session. Disconnecting a client doesn't stop the agent, and an in-flight task keeps running.
- State survives your machine: conversation history, bound repositories, and the sandbox's file state persist in the cloud. Reattach from any surface and the transcript replays where you left off.
- Approvals wait for you: if the agent needs permission for an action while nobody is connected, the request waits and is presented to the next client that attaches.
Prerequisites
- A paid Mind subscription (Pro or higher) — cloud sessions are included at no extra cost
- A connected GitHub account, if you want to work on repositories (GitLab coming soon)
Work with cloud sessions
In the IDE, cloud sessions live in the session rail showing a Cloud Sessions section alongside your local projects.
Start a cloud session
- Select + (New Cloud Session) in the Cloud Sessions section header.
- Optionally select Select repos below the composer to attach one or more repositories from your connected source provider.
- Choose your model, agent or workflow, and autonomy level (Autopilot or Autonomous).
- Type your first prompt and submit. Mind provisions the sandbox, clones the selected repositories, and sends your prompt.
Manage cloud sessions
From a session's context menu you can:
- Pin Session to keep it at the top of the section
- Open in Mind Web to continue the same session in the browser
- Open with Mind CLI to attach from a terminal
- Delete Session to permanently remove the session and its sandbox
What runs where
Cloud sessions draw a clear boundary between your machine and the sandbox:
| Item | Local machine | Cloud sandbox |
|---|---|---|
| Your prompts and attachments | Composed here | Delivered to the session |
| Repository code | Never uploaded | Cloned server-side |
| Agent file reads and edits | — | Run in the sandbox |
| Shell commands and builds | — | Run in the sandbox |
Project configuration (.mind/) | — | Arrives with repo clone |
Personal configuration (~/.mind/) | Stays local | Not applied automatically |
Configuration in the cloud
- Project configuration travels with the repo: steering, specs, custom agents, hooks, and MCP servers committed under
.mind/in your repository apply in cloud sessions automatically. - Local configuration can be applied to cloud sessions: your
~/.mind/directory isn't applied automatically. To use personal Steering, custom agents, Skills, Hooks, Agent Plugins, and MCP servers in cloud sessions, upload them from Configuration Sync in Mind Web settings.
Move between surfaces
| From | To | How |
|---|---|---|
| Web | CLI | mind --resume-id <session-id> |
| IDE | Web | Open in Mind Web on session menu |
| IDE | CLI | Open with Mind CLI on session menu |
| CLI | Web | Open session at app.mindcode.sh |
Limits
- Concurrency limit: you can run up to 10 cloud sessions in parallel.
- Repository set is fixed: the session works on the repository it was created with.
- No Supervised mode: cloud sessions run in Autopilot or Autonomous; per-change approval isn't available.