Sessions (save and resume)
Every interactive run is a session. Wayland Core records the conversation so you can leave, come back, and pick up where you stopped. Sessions are stored on disk and indexed by an ID.
List what you have
Section titled “List what you have”wayland-core --list-sessionsThis prints saved sessions newest first, with the ID you pass to --resume.
Resume a specific session
Section titled “Resume a specific session”wayland-core --resume <SESSION_ID>The engine loads the full message history for that ID and continues the conversation in the same context.
Continue the latest
Section titled “Continue the latest”When you just want to keep going with the most recent session, use the shortcut:
wayland-core -c # long form: --continue-c resolves to --resume <latest-id> for the session with the newest creation time. It is mutually exclusive with --resume and --session-id: pass one, not several.
Pin an ID up front
Section titled “Pin an ID up front”By default each new run generates its own ID. To control the ID yourself, for example so a script can resume a known session later, set it explicitly:
wayland-core --session-id nightly-report "Summarize today's commits"A later run with --resume nightly-report reopens that exact conversation.
Where sessions live and how many are kept
Section titled “Where sessions live and how many are kept”Session persistence is governed by the [session] config section. It controls the storage directory and max_sessions, the cap on how many sessions are retained before the oldest are pruned. See Configuration for the full section.
[session]max_sessions = 20If you run with sessions disabled in config, the engine still works for one-shot and interactive use; there is just nothing to resume.
Inspect a session’s memory
Section titled “Inspect a session’s memory”To dump the memory state recorded for a session (episodes, project facts, procedures) as a plain text table for inspection:
wayland-core --memory-show <SESSION_ID>