Agnai suits roleplay writers who want configurable characters and model connections, but guest mode needs a deliberate backup plan. A character export, a chat export and a guest-workspace backup preserve different things. Choose the scope before changing browsers or clearing site data; a character file alone will not preserve your ongoing story.
A saved guest character survived reload; that is not a backup
Observed October 24, 2026 · Hosted web app · Logged-out guest
We created Maple Backup Test 2026-10-24, a fictional adult cartographer whose scenario included a brass compass named Cedar-47. After saving and reloading the page, the character remained in the list. Reopening its stored definition in the Copy a Character form showed the name, scenario and greeting we had entered.
This established persistence through one reload in that browser. It did not establish cross-device access, recovery after cleared storage, or whether a model would remember the compass. We did not generate a response.
The official local-running guide says anonymous data lives in browser storage, does not travel automatically between browsers or devices, and can be deleted by clearing the browser’s application data or cookies. The quick-start guide points to an account for cross-device access. Neither statement establishes what happens to an existing guest workspace when you sign in.
“Prepare Backup” reveals the next control
In You → profile → Guest Data, our fresh guest session first showed Backup Not Ready. Selecting Prepare Backup made Download Guest Data available. That extra preparation step matters: seeing a saved character in the app is different from having a file outside that browser.
For our character without an avatar, the separate export dialog offered Tavern, Agnaistic and Textgen, with JSON as the only available file type. We did not confirm a completed file download or inspect exported contents. The controls were observed; file validity and restore remain untested.
Choose a character, a conversation or the guest workspace
On a narrow screen, scroll this table sideways. Keyboard users can focus the table area and use the arrow keys.
| Your task | Relevant export | What its implementation covers |
|---|---|---|
| Reuse a persona in another setup | Character export | The selected character definition. It is not a copy of the conversations you had with that character. |
| Keep one ongoing story | Chat export | The selected chat's messages and context. It is not a backup of every guest character or setting. |
| Preserve the broader guest workspace | Guest Data backup | Characters, chats/messages, presets, profile/configuration, books, scenarios and templates. |
The scope map comes from Agnai’s public implementation: character export, chat export and guest backup. We checked that pinned June 13 revision on October 24; source inspection does not prove that every part matches the hosted deployment or that a restore succeeds.
The character-export implementation makes image-card output conditional on an avatar. Our no-avatar JSON-only dialog therefore does not establish that Agnai lacks image-card export. Format names also do not establish full compatibility with another app; fields can differ.
My practical choice: keep the guest-workspace backup for recovery and a character export for portability. They solve different problems. A story transcript can be useful as a separate reading copy, but it should not be treated as a restorable workspace unless its import path has been checked.
Guest import warns of replacement
Do not import a guest backup over the only copy of work you want to keep. The profile implementation warns that importing replaces existing guest data. We did not execute that operation.
This is the easy mistake when you have started a new story in a second browser and then try to bring the old workspace across. “Import” can sound additive; the warning describes replacement. Preserve both workspaces independently before considering it, and use a separate browser profile containing only disposable test data for a recovery rehearsal.
Suggested recovery rehearsal · Not performed in this review
- Create one nonsensitive character with a distinctive scenario and greeting. Note which fields you expect to retain.
- Choose the export scope from the table. Keep the original browser data intact and verify that a file actually exists outside the browser.
- Check the destination's supported import format. For a guest-workspace import, read the replacement warning before continuing.
- Use a separate disposable browser profile. Compare the restored fields and, where relevant, conversation messages and settings with your notes.
A successful character import would establish only that character's transfer under those conditions. It would not verify chat history, the entire workspace or another app's handling of every field. Until a recovery check succeeds, keep the original working copy.
Browser storage does not tell you where the model runs
Guest mode describes storage, not inference. Agnai’s local-running guide says a locally hosted interface still needs an external AI service unless you run a model yourself. It also says self-hosting does not include access to Agnai’s subscriber models. The hosted quick-start guide describes Agnai as the default model service.
Before using private writing, check the selected AI service and its own data handling and content rules. Saving character data in a browser does not establish that prompts stay on your device, that the service retains nothing, or that generation is free. We did not inspect traffic, test a self-hosted installation or assess model quality.
If you want a different character frontend, compare SillyTavern’s setup and file boundaries. If your main requirement is local model execution, the Ollama review explains the separate local/cloud choice. Switching the interface alone does not settle either question.
Next step: protect one small sample before moving your story
Start with a disposable character, then verify the file and destination you actually need. Use character export to move a persona, chat export for one conversation, or Guest Data for the broader guest workspace. Keep the working browser intact until you have checked the result in an isolated destination.
Agnai is worth shortlisting when you want those configuration choices and can manage the model connection and your data. If you expect guest mode to sync or recover itself, settle that requirement before investing a long-running story in it.