Docs

Appearance

CharacterVault 1.4.5 ​

A patch on 1.4.2: Orion and Agent chats stay with the character or lorebook you opened them on.

Try it: https://vault.charactervault.app
Staging: https://staging.charactervault.app
Docs: https://vault.charactervault.app/docs/

Highlights ​

Saved chats ​

Ask Orion and the Agent keep a thread per character and per standalone lorebook. Close the panel, switch cards, or come back later — the conversation is still there.

  • Orion and Agent stay separate. New chat on one panel does not wipe the other.
  • New chat asks first, then clears only that panel’s saved thread. Leaving or closing the panel aborts a live run and keeps the transcript.
  • Load earlier messages pages older turns back in. The on-screen window stays small; the rest stays in the browser.
  • Threads live in IndexedDB with the rest of the vault. They are not written into PNG/JSON export or the vault ZIP backup. Deleting a character or lorebook deletes its chats with it.

AI Assistant → · AI Agent →

Also in this patch ​

  • Closing Ask AI on a character unmounts that chat so a switch cannot leak the previous transcript or a write still in flight.
  • Each thread keeps at most 500 saved messages. If browser storage is full, CharacterVault trims the oldest half of that thread and retries once, and shows a Chat not saved toast.
  • Opening a card after a failed history load no longer looks like an empty writable thread. Send stays blocked until the saved tail can be read.

Upgrade ​

Client-only app. Open the hosted site or rebuild locally; no server migration.

bash
git clone https://github.com/spaceman2408/CharacterVault
cd CharacterVault
npm install
npm run dev

Local data from 1.4.2 keeps working. IndexedDB gains a chatMessages table the first time you open this build (schema versions 11–13). Existing cards and lorebooks are unchanged; chats start empty until you send.

Hard refresh if the UI looks stale after deploy.

Docs ​

Privacy

Copyright © 2026 spaceman2408