sessions

kolega-code sessions manages the local session records that the TUI and ask --save create. Sessions hold the conversation history, the project they belong to, and the model configuration in use.

kolega-code sessions <list|delete|export> [options]

See Settings & API Keys for where session files are stored, and Sessions & Resuming for how resuming works in the TUI.

sessions list

List saved sessions, optionally filtered to one project.

kolega-code sessions list --project .

Option	Description
--project <PATH>	Only show sessions for this project
--state-dir <PATH>	Directory for CLI session state

Each saved session is shown as a labeled block:

Updated:   2026-07-19T10:00:00+00:00
Title:     Improve session listing
Mode:      code
Project:   /path/to/project
Resume ID: 0123456789abcdef0123456789abcdef

Sessions are ordered from oldest to newest, so the most recently updated session and its Resume ID appear nearest the shell prompt. Pass that Resume ID to --resume, sessions delete, or sessions export.

sessions delete

Delete a session by ID.

kolega-code sessions delete <session_id>

Argument / option	Description
session_id	The Resume ID shown by sessions list (required)
--state-dir <PATH>	Directory for CLI session state

sessions export

Print a session as JSON, or write it to a file.

kolega-code sessions export <session_id>                 # to stdout
kolega-code sessions export <session_id> --output run.json

Argument / option	Description
session_id	The Resume ID shown by sessions list (required)
--output <PATH>	Write JSON to a file instead of stdout
--state-dir <PATH>	Directory for CLI session state

The exported JSON includes the session metadata, model configuration summary, and full message history — handy for archiving, debugging, or analysis.