Skip to content

CharacterVault 1.8.3 ​

CharacterVault 1.8.3 adds clickable variable chips to every prompt template, keeps linked lorebooks in sync both ways, and makes Settings ask before throwing away unsaved changes, plus Paste from Clipboard on import and a round of Settings and lorebook fixes.

Try it: https://vault.charactervault.appStaging: https://staging.charactervault.appDocs: https://vault.charactervault.app/docs/


Highlights ​

Prompt variable chips ​

Every prompt template in Settings → Prompts and Settings → Creation Studio → Generation Prompts now lists its variables as chips under the text box, with plain names like Selected text, Concept, or Style rules instead of ${…} code.

  • Click to insert — a chip puts its variable at the cursor, or at the end if you haven't clicked into the prompt.
  • Click to find — if the prompt already uses that variable, the chip selects it in the text instead of adding a second copy. Click again to step through each use.
  • Status at a glance — green when the prompt uses it, red when a required one is missing, and a plain + for optional ones. Hover a chip to see what it holds and whether it's required.
  • Everywhere ${…} is used — the built-in toolbar prompts, your custom buttons (including New custom button), and all four Creation Studio prompts.

AI Creation Studio → Generation Prompts

Two-way lorebook sync ​

A character linked to a library book (character → Lorebook → Attach) now sends its lorebook edits back to the library.

  • Edits sync on save — hand edits, Agent writes, Copy, and snapshot restores on the character update the library book and every other linked character, in save order.
  • No stale opens — leaving the character finishes the sync first, so the library never opens an older version.
  • Unmatched characters stay put — a character linked without copying keeps its own entries until you click Open in vault.
  • Safety snapshot — Open in vault saves an Auto snapshot of the library book before overwriting it, only when the push changes it.

Lorebook Vault → How they stay in sync

Settings that keep your changes ​

  • Ask before closing — closing Settings with unsaved edits asks first: Keep editing or Discard.
  • No blind saves — Save Settings stays off until settings finish loading. If loading fails, Try again reloads them, so nothing gets overwritten with defaults.
  • Backups restore fully — restoring a settings backup keeps the endpoint's stored API key and your editor font size.

AI Setup

Also in this release ​

  • Paste from Clipboard — when the import page can't read the clipboard on its own, a Paste from Clipboard button appears above the paste box, and errors say what went wrong.
  • Referral sign-up links — Settings → AI Config → API Key shows New? Sign up (referral) next to Get your key for NanoGPT and Synthetic. The tooltip names the perk.
  • Support on Ko-fi in the vault footer.

Fixes ​

  • Confirm dialogs cover the whole window, so the AI Context and chat panels can't be clicked behind them.
  • Prompt model routing — a routed prompt's model no longer carries over to a new endpoint, model fetch errors show under the picker, editing a custom endpoint's URL keeps its key and model, model lists that finish loading after you change the base URL are ignored, and save errors name the buttons.
  • NanoGPT sign-in saves the key under the endpoint you started sign-in from.
  • Settings traps keyboard focus as soon as it opens.
  • Custom buttons can't reuse the label of a hidden built-in.
  • Custom context length can be cleared while typing.
  • Attached lorebooks — the attach panel closes when a confirm opens, Copy reads the latest library book and builds on the latest saved card, Orion and the AI toolbar no longer get the linked book twice, and entry counts read "1 entry".

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.8.2 keeps working. Hard refresh if the UI looks stale after deploy.


Docs ​

Privacy