Chats commands

These commands read the same conversations as the Conversations page. Like the other project-bound commands, the project id comes from cassis/project.yml in the checkout, CASSIS_PROJECT_ID, or --project. Both commands only read: they never start an analysis or a model call.

chats list

Lists the conversations you can read, latest message first. One line per conversation: its id, review status (Not analyzed, In progress, Needs attention, or Analyzed), feedback counts (up 1 / down 0), the time of the last message, and the title, followed by its link in the web app. The id is what chats show takes.

# The 20 most recent conversations
cassis chats list

# Only the ones whose review found a problem
cassis chats list --review needs-attention

# Conversations with a thumbs down since a date
cassis chats list --feedback down --since 2026-11-01

# Find by title, author name, or email
cassis chats list --search "active customers"

# Next page
cassis chats list --limit 50 --offset 50

# Raw JSON, with links and pagination
cassis chats list --json

Filters

--feedback (up, down, any, none), --review needs-attention (conversations whose analysis detected a problem; improvement suggestions alone do not count), --since (an ISO date or timestamp for the last message; dates are read as UTC), --search (title, author name, or email). All optional and combinable.

Paging

--limit (1 to 100, default 20) and --offset. The footer says how many of the total were printed and the offset of the next page when there is one.

Links

Each line is followed by the conversation’s URL in the web app. --app-url changes its base when the app is not served from the API URL.

Output

One line per conversation, or the page as JSON with --json, which carries items, total, offset, and next_offset.

chats show

Prints one conversation, message by message, followed by its saved analysis: the observations, the supporting quotes taken from the conversation, the suggested next steps, and the issue linked to it when there is one. When the latest analysis is still running or did not complete, the previous completed one is shown.

cassis chats show 019f0000-0000-7000-8000-0000000000c1

# Add compact previews of each execution step
cassis chats show 019f0000-0000-7000-8000-0000000000c1 --trace

# Print one execution step in full
cassis chats show 019f0000-0000-7000-8000-0000000000c1 --trace-entry trace:019f0000-0000-7000-8000-0000000000m1:3

# Only the analysis
cassis chats show 019f0000-0000-7000-8000-0000000000c1 --analysis-only

# Everything as JSON, traces complete
cassis chats show 019f0000-0000-7000-8000-0000000000c1 --json

Traces

--trace adds a bounded preview of every execution trace entry under its message, each labeled trace:<message-id>:<index>. --trace-entry prints one of them in full, as JSON. Neither combines with --analysis-only.

Output

The conversation and analysis as text, or with --json the full record: messages, complete traces, and the analysis. With --analysis-only --json, the analysis alone.

Exit codes

1 when the conversation is not readable in the project or the trace entry does not exist, 3 on transport errors.