> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clideck.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Search & Filter

> Find sessions quickly with search and tab filtering

Two ways to find sessions in the sidebar: text search and tab filtering.

## Search

The search bar at the top of the sidebar filters sessions as you type. It matches against:

* **Session name** — The name you gave the session (or the auto-generated one)
* **Transcript content** — Everything the agent has output during the session

This means you can search for a function name, error message, or file path and find the session where you worked on it — even if you didn't name the session after it.

Search updates instantly as you type. Clear the search to see all sessions again.

## Tab Filtering

Below the search bar, two tabs filter the session list:

* **All** — Shows every session
* **Unread** — Shows only sessions with new output you haven't looked at yet. A count badge shows how many unread sessions there are.

## How Unread Works

A session is marked as **unread** (blue dot in the sidebar) when it produces new output while you're looking at a different session. Clicking on the session marks it as read.

This helps when you're running multiple agents — you can quickly see which ones have produced new output since you last checked.

## Transcript Store

Behind the scenes, CliDeck records a searchable transcript for every session:

* **User input** is captured keystroke-by-keystroke and recorded when you press Enter
* **Agent output** is batched (300ms debounce), stripped of ANSI formatting codes, and stored as plain text
* Transcripts are saved as JSONL files in `~/.clideck/transcripts/`

The transcript powers sidebar search. It's plain text only — no terminal formatting, colors, or control sequences. This makes search fast and results relevant.

<Note>
  Transcripts are stored locally on your machine. They're used only for search functionality within CliDeck.
</Note>
