Backup and recovery#
This page names the recovery paths supported by the product. What it deliberately does not do is invent a whole-profile backup feature: if a mechanism is not listed here, it is not supported in this build.
What is this for?#
Knowing what would be lost if a machine died, and what the supported restore paths are.
Where your data lives#
| Data | Where | Backup path |
|---|---|---|
| Chats and activity | The app's runtime data store on this machine | Export a conversation (see below) |
| Workspace files and memory | They are your files, on your disk, inside the workspace | Back them up like any other files |
| Credentials | The encrypted credential store; keys never leave it | Re-enter keys on a new machine; there is no key export by design |
| Wallet keys | Sealed in the wallet's custody store | The recovery phrase you wrote down at creation |
The supported recovery paths#
- Conversations. Any single conversation can be exported to TXT or Markdown from the chat's export action. The export is previewed first and states exactly what it contains; it is a copy for keeping, not a restore target.
- Projects and files. A project's files are ordinary files in the folder you bound. Whatever backup you keep for that folder is the backup for the project.
- Wallet. A VOOL Wallet is recovered only with the recovery phrase shown exactly once at creation. There is no export door and no second reveal — by design. If you did not save the phrase, do not send funds to that wallet. See Wallet.
- The app itself. Updates roll back on failure and leave the previous app in place (see Updates and migration). A data store written by a newer VOOL is refused by an older one — the downgrade refusal is deliberate, part of keeping the store trustworthy.
What is not supported#
- No cloud sync or profile backup. Nothing about your usage leaves the machine to a VOOL-operated service, so there is no server-side copy to restore from.
- No wallet key export. "Nothing was revealed" is the contract on every export attempt; a watch-only or pilot wallet cannot export a key it does not hold.
- Restoring a copied data store by hand (copying the runtime data directory while the app runs) is not a supported mechanism; a store mid-write is not a consistent store.
What do I do next?#
Export the conversations you care about, keep normal file backups of your project folders, and store the wallet recovery phrase offline when you create a wallet. For a failure that names a code, see the Error Book; for reporting problems, Bug reporting and privacy.