Recovery & backups
Drafts, checkpoints and chat backups
Choose the right recovery tool: buffer, history, checkpoint or encrypted archive.
In this guide
Each recovery layer has a scopeMove conversations with a passphraseAutomatic-backup limitsEach recovery layer has a scope#
Drafts protect unsaved text; local history retains file versions; AI checkpoints cover files included in a proposal or turn; chat backups preserve conversations and metadata. These are not equivalent copies of the same content.
A disk conflict retains the draft and suspends autosave. Before restoring, review any later edits reported by the checkpoint. It does not undo effects on shells, databases or remote services.
Move conversations with a passphrase#
Import does not overwrite the current project or sources. Permissions and native links are not automatically reactivated. Plain JSON and readable Markdown exports are also available; choose the format deliberately.
- Open Conversation tools → Archives and backups.
- Choose a conversation or project export and Portable encrypted archive.
- Keep the passphrase separately from the exported file.
- To import, prepare the preview, map allowed folders and confirm creating a new project.
Automatic-backup limits#
Automatic backups are created while Code Weaver is open. On Windows the key can live in the profile’s credential vault; backups protected this way are not portable archives for another PC. Use a passphrase for transfers.
Chat backups do not include Codex credentials, sources, unsent drafts or every checkpoint. Protecting the repository and computer requires a separate backup strategy.