Skip to main content
A session is a named conversation thread. Each session has its own isolated chat history and short-term memory context. You can have as many sessions as you need — for example, one per course, one per project, or one per document set.

​
Managing sessions from the CLI

CommandDescription
:sessionsList all sessions with labels, IDs, and message counts.
:new [label]Create a new session. Switches to it immediately.
:switch <n>Switch to session number n (1-indexed, as shown by :sessions).

​
Listing sessions

:sessions
Each row shows the 1-based index, the session label, a truncated session ID, and the last-active timestamp. The active session is highlighted.

​
Creating a session

# Auto-named session-N
:new

# Named session
:new biology-revision
The new session is immediately active. Its label appears in the prompt box.

​
Switching sessions

:switch 2
Quark confirms the switch and shows the message count for that session. Use :sessions first if you are unsure of the index.
Each session has its own chat history. Switching sessions does not carry over the conversation context from the previous session.

Build docs developers (and LLMs) love

Get started for freeTalk to us