Sessions

Conversations are persistent. The CLI remembers your active session so context carries across messages — and even across separate cos invocations.

How sessions work

Every chat turn is tied to a session_id. The first message starts a session; the CLI stores it locally and reuses it on your next message, so the model keeps the full context. This maps directly to the Sessions API and Conversations API.

List conversations

bash

cos sessions

text

  Sessions (2 of 2)
  ► Auth questions        4 msgs · 2m ago · 25f37117
    SQL review            2 msgs · 1h ago · 9ab41c02

The ► marks the active session.

Switch the active session

Pass an id, or run it with no id to pick from a list (↑ / ↓ + Enter):

text

❯ /session use            # arrow-key picker
❯ /session use 25f37117   # switch directly

Read a transcript

bash

cos history

Start fresh

/clear (or /new) drops the local pointer so your next message begins a brand-new session. Delete one entirely with /session delete <id>.

text

❯ /clear
  Started a new session.

On exit the shell prints a resume hint — run cos session use <id> later to pick the conversation back up.