Sessions, context and undo

Sessions

Every conversation is a session, kept on your machine. You can leave and come back to it: /resume and /fork open a picker in the interactive screen, and talos --resume last continues the most recent one from the shell. A fork starts a new session from a copy of an existing one, so you can try another way without losing the first.

Sessions can be named, tagged and pinned, searched, exported for your own records (JSON, JSON Lines or Markdown), and shared: talos session share writes a copy with the keys and secrets found in your environment removed. An imported session — from the CLI or from TALOS Desktop — is a read-only archive: it never runs anything by itself. Every operation is on talos session.

Context

A model reads a limited window of text. With a model whose window is known and at least 64k tokens, a long conversation is compacted when it reaches half of the window, and the screen says when and how much. /context shows how full the window is; /compact compacts now; talos session context <id> says when a session will be compacted.

Undo

Before TALOS changes a file, it takes a checkpoint — kept outside your repository and outside Git, so your history is never touched. /undo restores the files a turn changed. From the shell, talos checkpoint list shows the checkpoints of the project, undo restores one, and redo applies again what an undo removed. See Undo what a turn changed.

Memory

What TALOS should remember from one session to the next is kept apart, in its memory: list, search, add, update and delete it with talos memory, or /memory in the interactive screen.