Borealis Docs

Import and export workspace files

Use workspace transfers to move files under /workspace. Use an environment snapshot for supported installed environment state.

Export before replacing data

From a running, accessible sandbox, export to a local archive:

borealis sandbox workspace export SANDBOX_ID --output ./workspace.tar

Check that the command completed and that the archive contains the files you expect before relying on it. Review the configured workspace sync policy, including ignore rules; do not assume every ignored or mounted file is part of a transfer.

An export can contain source code, configuration, and sensitive data. Store it with appropriate access controls and remove local copies when they are no longer needed.

Import into a sandbox

borealis sandbox workspace import TARGET_SANDBOX_ID ./workspace.tar

Review the destination ID carefully. The default import flow can clear the existing workspace, so preserve existing files first and read the confirmation before continuing.

The CLI also supports --keep to avoid clearing the workspace first. This is not a guarantee against overwriting files with matching paths. Consult borealis sandbox workspace import --help for wait and timeout options.

Pause processes that are writing to the destination while replacing files. When import finishes, verify the expected paths and restart any application that needs to reload them.

Follow transfer progress

Public clients use a resumable upload flow with an upload handle, chunk offsets, integrity checks, and a separate completion step. An uploaded archive is not necessarily an applied workspace.

Retain the upload or operation identifier when a transfer is interrupted. Query its status before starting a second import. File size, storage, and request limits still apply.

Use the supported transport

Use the CLI for workspace transfers, or integrate with the public API’s resumable upload and export-resource flows. Transfer archive bytes through those dedicated endpoints rather than embedding them as base64 JSON.

A workspace archive does not include the installed root filesystem or a running process’s memory. For a fuller restore workflow, pair it with an environment snapshot.