Branches and rewinding · Chazz.ai

How branches and rewinding works on Chazz.ai. Regenerate a reply and the story forks. Each branch keeps its own history and its own memory. Regenerating does not overwrite history. It forks the conversation: the old reply stays on its own branch and the new one starts a new branch from...

Regenerate a reply and the story forks. Each branch keeps its own history and its own memory.

Regenerating does not overwrite history. It forks the conversation: the old reply stays on its own branch and the new one starts a new branch from the same point. You can move between them.

What a branch carries

The lineage walk is exact: from the branch up through its parents, including each parent's messages only up to the fork point. Source: worker/src/engine/store.ts:104 visibleBranchMessages.

Every regeneration is a fresh generation and is billed as a normal turn. Producing five variants of one reply costs five turns.

Its own visible transcript: its inherited history up to the fork, then its own messages.
Its own engine state: session, world clock, and living memory.
Nothing from a sibling branch. A fork never sees what a parallel version of events said.

Multi-character regeneration

In a chat with several characters, regenerating streams the new beats onto the forked branch, so the alternative version stays coherent across the whole cast rather than only replacing one line.

Elsewhere on Chazz.ai

This document is the server-rendered form of /docs/branches-and-rewinding. The interactive page needs JavaScript, and shows the same content.

The complete documentation of this service is available as one plain-text file at /llms-full.txt. A short summary, with the operator's policy for automated readers, is at /llms.txt. Changes are published as a feed at /rss.xml.

Chazz.ai is operated by Cognitive Industries, ABN 62 794 528 747, Australia. Contact: [email protected].