Skip to main content

What comes across

One pass over your profile folder brings:
  • Characters, with the lorebooks embedded in their cards linked as it goes
  • Sprites, each pack landing on its character, labelled by filename
  • Personas, name and description read out of settings.json beside their avatars
  • Chats, with every swipe kept as a branch
  • Worlds, as lorebooks
  • Backgrounds
A card’s standard fields all arrive. What sits outside them does not: talkativeness, depth prompt, the card’s own world link, favourites. Chats keep their swipes, their reasoning, the model that wrote each turn and how long it took; prompt token counts are not in the file to recover.

Importing your folder

Settings → Import, then choose your profile folder, data/default-user. Pick that folder itself. The one above it is refused rather than searched, because the browser walks every file under whatever you pick before ChungusHub sees any of it. You get a count of what was found before anything is written, and a summary after. A file that fails is named in that summary rather than skipped in silence, and a chat whose character is not in the library is listed so you can import the character and run it again. Run it a second time and only new files come over. If you deleted something and want it back, tick the box that includes what the folder has already sent. Single files work too, wherever the thing lives: a character card in the Library, a world info file in Lorebooks, a regex script in Settings → Regex.

What is the same

  • Card formats. V2 and V3 cards import, as .json or as a PNG. Exports are valid V2 cards that SillyTavern reads back.
  • World info. Read and written in SillyTavern’s native format, and the fields ChungusHub does not model ride along untouched instead of being dropped.
  • Macros. {{char}}, {{user}} and <START> example blocks mean what they mean there.
  • Sprite layout. characters/<Name>/<label>.png, so a pack moves either direction by being dropped into a profile’s characters/.
  • Regex scripts. They import, and depth bounds count turns back from the newest on both sides.

What works differently

  • A chat is a tree. Swipes are branches rather than a carousel: an edit or a regeneration adds one instead of replacing what was there, and the story map is how you move around it. Imported swipes arrive as exactly that.
  • Hidden turns come back visible. There is no per-message hide here, so a turn SillyTavern was keeping out of the prompt imports as an ordinary one.
  • Nothing rewrites a stored message. A regex script set to rewrite permanently applies to what you read and what is sent instead, leaving the message as it was written.
  • Connections instead of one API profile. Several live side by side and each part of the app can point at a different one, so a cheap model does the background work while your story runs on another.

What is not here yet

  • Group chats. One character to a chat for now.
  • SillyTavern’s own settings. Presets, sampler configs and instruct templates do not import. ChungusHub’s presets are its own format.
  • Chat export. Chats come in and do not go back out.
  • Extensions. The extension API is still on the roadmap, so there is nothing for a SillyTavern extension to attach to.