session

Overview ¶

Command session walks one weft/thread session through its whole life: two turns, a label, a branch off the first answer, a fork of the branch, a manual compaction with preview, a close, and a reopen from disk — everything on a JSONL backend, everything offline through a scripted model, every id deterministic.

By default the session files go to a fresh temporary directory that is removed when the command exits, so it can be run any number of times; -dir keeps them somewhere you can read them.