​
Overview

Every interaction with Gizzi Code happens inside a session — a persisted conversation context that includes messages, tool calls, traces, and metadata. The gizzi session command group lets you manage those sessions directly from the terminal: list recent work, export a session for offline analysis or sharing, and remove sessions you no longer need. Sessions are typically created when you run gizzi, gizzi run, or gizzi exec. Use gizzi session when you want to inspect history without reopening the TUI, archive a transcript, or clean up disk storage.

​
Command reference

​
gizzi session list

Show your recent root sessions. In an interactive terminal the output is paged with less; in non-TTY environments it prints to stdout.
The JSON output contains one object per session:

​
gizzi session delete

Delete a session permanently. You must provide the full session ID.
Deletion is immediate and cannot be undone. Exported archives are not affected.

​
gizzi session export

Export a complete session snapshot as formatted JSON. The export includes session metadata, all messages and parts, and the session trace.
The exported JSON object has three top-level keys: Export is useful for attaching context to bug reports, importing into another tool, or keeping a long-term archive outside of Gizzi Code.

​
Common flags

​
Runtime session flags

Sessions are usually created and continued through gizzi run or gizzi exec. The relevant flags are: See Headless Execution for pipe-safe, non-interactive usage with gizzi exec.