State

Different kinds of state have different lifetimes, and Autolith keeps them in separate, readable stores instead of one database.

Conversations

Conversations are append-only readable files with exact resume commands and crash-tail repair. /resume picks one by title, /conversations lists them, and autolith replay ID reads a conversation without resuming or locking it:

terminal

$ autolith replay ID
$ autolith replay ID turn 12
$ autolith replay ID date 2026-09-01

Replay steps with next and previous and jumps by turn, date, time, or sequence. Every session also gets a title immediately, refined later by the provider if you allow it with /titles.

The vault

Steering messages and follow-ups typed around a crash survive in a conversation-scoped vault. The vault is deliberately not resubmitted on its own, because you may want to diagnose the crash first:

prompt window

(vault)         ; see what the vault holds
(vault-restore) ; resubmit follow-ups and steering messages
(vault-discard) ; delete the vault contents

Memories, agenda, papercuts

Memories: Workspace or global facts and preferences with bounded prompt recall. Ask Autolith to remember something, or write one yourself.
Agenda: The workspace's short durable task list, delivered in full on every request. /agenda shows it.
Papercuts: Reports Autolith files when something in the environment does not work. /papercuts lists them; /papercut-close resolves one.

These stores are read and written through resource URIs with revision gating: a read returns an observation with a revision, and an edit applies only against exactly that revision. Shared state transactions are serialized across processes, so concurrent agents can share one workspace.