How to save Chub AI chats separately from the character card

The character card is not the conversation archive

Chub documents chat exports in JSONL, PNG, and text formats from chat settings. Those exports preserve the chat record, while a character definition remains a separate layer.

For a long roleplay, pair the raw export with a current-state summary that tells you which branch and decisions should continue.

Signs it is time to make a continuity note

• You are branching a Chub chat or moving it to another compatible frontend.
• The character card is unchanged but the story has developed substantially.
• You need a backup before editing a prompt, model, or lorebook.

A practical Chub AI preservation workflow

Use Chub's current chat-export option for a raw record when available.

Give the relevant chapter to thredly for a structured summary of characters, events, decisions, and current objective.

Keep the summary with the export and bring it into Chat Memory or a new chat when continuation is the goal.

thredly is independent of Chub AI. It does not read Chub AI chats automatically. Copy a conversation section or use a native export when available, then paste or upload the text through thredly's supported web workflow.

What a useful handover should retain

• Character identity, personality, voice, and any user persona details that still matter.
• Names, relationships, boundaries, promises, preferences, and corrections that supersede earlier information.
• Important story events, locations, dates, running jokes, unresolved plot points, and the current objective.
• A short instruction for the next session that states where the conversation should resume.

Related guides

• Chub AI memory
• Never lose an AI conversation
• AI companion memory guide
• Save AI chat history

Frequently asked questions