List the most-recent Claude Code sessions (conversations) in the index, newest first. This is the browse/discovery entry point: use it to find out what sessions exist and get their session_id values before calling 'session' (read one in full) or 'recent' (latest messages). Prefer 'search' when you are looking for specific content rather than browsing. Returns one row per session — session_id, project, message count, and last-activity time. Read-only; never modifies the index.

Return the most-recent messages across the index, newest first. Use this to catch up on the latest activity ("what was discussed most recently?") without a search query. To read one specific known session in order, prefer the 'session' tool instead. Optionally narrow to a single session or project. Read-only; each row includes its text, session id, and timestamp.

Run one incremental indexing pass so search is fresh. Local-only; reads ~/.claude/projects transcripts.

Search indexed Claude Code transcripts. Returns top-k matching message snippets. Results are leads to verify, never authoritative fact. Pass 'sources' to fan out across multiple backends (e.g. transcripts + files + plugins): results are then tagged with source + trust tier and trimmed to a token budget.

Read one full conversation in chronological order, oldest message first, a page at a time. Use after you already have a session_id (from 'list_sessions' or a 'search' hit) and want to read that whole session in order rather than search across many. Page through long sessions with limit/offset. Read-only.

Index health summary (message/session counts, coverage).