Resume and export sessions

Sessions persist conversation and tool events. Use --continue for the latest directory session, --resume to select one, and --fork to create an independent continuation.

How do I branch or compact a long conversation?

In the terminal user interface (TUI), /tree shows the conversation structure, /branch or /fork creates another path, and /compact replaces older context with a summary. Inspect the summary before relying on it.

How does project memory differ?

Memory holds durable project facts across sessions; a session holds one conversation history. Start with --no-memories when stored context must not influence the run. Keep credentials and transient outputs out of memory files.

How do I export a record?

Run xcsh --export <SESSION_FILE> to create HyperText Markup Language (HTML) from a session file. Review the export for sensitive content before sharing it.

Resume selects an existing leaf; fork creates a new branch from a chosen point; compaction summarizes older context for later model turns without deleting the append-only record. Export before moving or deleting a session you may need as evidence. Project memory is authored guidance loaded by scope, not a replay of session history. After a branch or compaction, ask a bounded context question and inspect the session tree to confirm the intended lineage is active.