#
Workspace data and restarts
#
The one rule
Everything under /workspace is kept. Everything else is rebuilt when the
workspace restarts.
Your workspace has a single persistent volume, mounted at /workspace. It
survives restarts, upgrades and redeployments. The rest of the system,
including your home folder and /tmp, starts fresh each time.
#
What survives a restart
#
When a workspace restarts
Workspaces restart for platform updates and maintenance, which means a short interruption. There is nothing you need to do: everything in the left-hand column above carries over.
#
If the agent was working
A task the agent was in the middle of is not lost. After the restart, the agent picks it up again on its own, with the note "The server restarted while you were working". If a task keeps getting interrupted, the agent stops retrying after 10 attempts.
Open terminals do end with the restart. In the Terminal tab, use Sessions → Continue last session to follow the conversation again.
#
Installing tools so they last
Because only /workspace is kept, install what a project needs inside the
project:
- Project dependencies such as
node_modules, a Python.venvor avendorfolder live in the project folder and are kept. - Global tools, installed with
npm install -g,pip install --useror downloaded into your home folder, disappear at the next restart.
For a tool you need in every session, add it as a project dependency, or keep a small setup script in your repository and ask the agent to run it after a restart.
#
Backup and restore
Back up your workspace from Settings → General:
- Export settings downloads your settings only.
- Export all downloads the whole workspace, including every checkout and your conversations.
- Import restores an exported archive. Each top-level folder in the archive replaces the folder of the same name.
Use Export all before an import, or before you remove a workspace, so you can always go back.
#
Disk space
A workspace starts with a 5 GiB volume. Your checkouts, conversations, CodeGraph indexes, the browser's profile and attached files all share it.
To see how much is in use, run df -h /workspace in a terminal. To get more
space, contact support; the volume can be
expanded.