Data and backups

Know the defaults

Recovery sessions live in API memory by default and disappear when that process stops. The integrated bridge does not expose durable-session controls. The Angular app supports JSON backup and restore, Markdown summaries and opt-in disk saving.

Back up before stopping or upgrading

In the Angular app, download a JSON backup to preserve a restorable recovery session. Export Markdown for a readable summary; it is not a restorable backup. Store downloads privately outside Git. Restoring JSON creates a memory-only session; saving must be enabled again explicitly.

Opt into local saving

REBOUNDOPS_DATA_DIR="$HOME/.reboundops/sessions" npm run dev

Use a private, non-synced directory outside the checkout. In the Angular app, choose Enable local disk saving for this session. Configuring the folder alone does not save a session. After restarting, use Resume session to reopen an opted-in record.

Delete copies deliberately

Deleting a saved session removes its in-memory record and saved session file. Turning saving off removes its disk copy but keeps the session in memory. Downloaded backups, schema-upgrade backups and other copies require separate deletion.

Workspace records need a separate private backup of the files you use; recovery exports do not include them. Read saving and recovery details ↗ and privacy guidance ↗ before using personal data. If saved files are skipped, stop the API and make a private copy before investigating; do not publish the files in an issue.