Work offline and recover edits
This page covers what a cloud project keeps on your device: which files download, what automatic cleanup removes, what works during a disconnect, and how to recover edits that haven't reached the server.
Edits to shared text files sync as you type, and the file stays unsaved until you select Save, which records a version in file history. Desktop keeps edits that haven't synced on this device and sends them when the connection returns. If your access changes or the file is replaced in the meantime, Desktop holds the edits for review or recovery.
The document status shows whether your edits are still syncing or only on this device. Recovery data is written in small batches; while the status says local changes are still being saved, the latest batch hasn't been written yet.
See Work together live for shared editing, cursors and Follow.
Files download as needed
Opening a cloud project loads its file tree and fetches file contents as needed. It does not create a complete offline mirror of every source file, dataset, package, and run artifact.
The installed application keeps downloaded cloud files on disk. Reopening a cached file can use that copy; a project update invalidates an outdated clean copy so a later read fetches current content. Pending local work is preserved rather than replaced by an incoming file notification.
The browser uses browser-managed storage for editor recovery and temporary caches for filesystem access. It does not use the installed application's native disk cache. Local folders use the actual files on your computer.
What automatic cleanup removes
The disk cache keeps up to 10 GiB of downloaded files per project and removes the least recently used clean files first. Edits that haven't reached the server are never removed. See Work with large projects and data for every cache, its limits and how cleanup works.
During a disconnect
You can continue editing an open shared text document during a disconnect. Documents you opened previously can also reopen if their recovery data is still on this device. Opening a document for the first time, or after its cached copy has been removed, may require a connection.
When the connection returns, RunMat reconnects and syncs pending edits. If the file was replaced, deleted, or your access changed, the app offers review or recovery rather than applying those edits over a different document.
The installed application also keeps file uploads queued on disk until they succeed. After network failures or temporary server errors, it retries automatically with increasing delays. Further writes join the queue; updating your sign-in credentials prompts another attempt. If an upload fails because of permissions or a conflicting file change, it stays queued until the problem is resolved.
Uploads continue while the application is running. After quitting, reopen the cloud project to resume pending uploads.
Offline availability and runs
Running code offline requires its dependencies, datasets, and packages to be available on your device too. Runs in a shared cloud project need a connection to capture their inputs, even if the source file is cached.
For offline runs, use a local project with its dependencies and data on your device. Back up important local work separately.
Recover work safely
Open the document status to retry a connection or download a recovery copy. Local recovery also lets you find pending work from closed, deleted, or replaced documents. Sign in to the account and project where you made those edits, on the same device.
If storage is full or a local recovery write fails, resolve the error before treating the latest edits as safely recoverable. See Troubleshooting for the available recovery actions.