DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to back up your Talorys data and restore it later with Talorys

Download a backup file of your data and import it into another install.

Who it is forAn owner who wants a copy of their chats, memories, tasks and automations before an update or a move.

The problemYour history and settings live in one Durable Object, so losing access to that install would mean losing everything.

The outcomeA talorys-backup.json file you can keep, and a merged import that does not duplicate or overwrite your edited memories.

What you need first

  • Node.js 22 or newer
  • A Cloudflare account, with browser login or an API token that has the listed permissions
  • A password you choose for the owner account
  • A terminal on your computer

Steps

  1. Open Settings, then Privacy, and choose Download backup to save talorys-backup.json.
  2. Store the file somewhere safe, knowing it contains your personal data but not sessions or credentials.
  3. To restore, open Settings, then Privacy, and choose Import on the target Talorys install.
  4. Check the import result, which lists any settings it skipped.
  5. Re-open Automations, because imported automations arrive paused and must be turned back on.

Prompt for your agent

In the Talorys app at <pages-dev-url>, download a backup from Settings > Privacy and save it as talorys-backup.json. Report the file size and the counts of conversations, memories and tasks if shown. Verify the file opens as valid JSON and contains an automations list.

Caveat. The backup file holds your personal conversations and memories in plain JSON, so store it as carefully as you would store private notes.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page