Sandboxes
Every project gets an isolated cloud sandbox (micro-VM style environment) with its own filesystem and processes.Why isolation matters
- Your dependencies and processes do not collide with other users
- The agent can install packages and run servers safely for that project
- Preview and terminal always target your machine
Idle pause
Sandboxes auto-pause after idle time to save resources. Limits by plan:
When paused, state is preserved. The next interaction (open workspace, agent run, file access) resumes the sandbox.
What survives pause
- Project files and git history
- Configuration and env vars stored for the project
- Published deployments (separate from the sandbox)
Practical tips
- Long idle tabs may need a moment to resume
- Heavy installs are fine — prefer asking the agent rather than fighting the terminal unless you are comfortable
- If resume fails, refresh and retry; contact support with the project ID if it persists