search-chats

CC Search Chats

A Claude Code plugin that lets you talk naturally about past sessions and get answers. No special syntax needed — just describe what you're looking for.

Features

• Conversational Access — Ask about past sessions in plain English and the agent finds them
• Session Recall — Paste a session ID and pick up where you left off
• Filtered Extraction — Ask for specific parts of a session and get only what matters
• Cross-Project Memory — Search across all your projects, not just the current one
• Local LLM Analysis — Pipe extracted content to llama.cpp for deeper analysis
• Session Cleanup — Remove specific sessions from history

Use Case: Session ID from Your Status Bar

With ccstatusline-usage your status bar shows the Session ID at all times:

  Session: [██░░░░░░░░░░░░░] 11.0% | Weekly: [█████████░░░░░░] 57.0% | 3:47 hr |  | Model: Opus 4.6[1m]
  Session ID: 26083761-5c49-4a70-a2ec-8526f05c65f6
  Context: [░░░░░░░░░░░░░░░] 30k/1M (3%) | Pace: [░░░░░██|░░░░░░░] D7/7 -28%

Copy that Session ID and mention it naturally in a new conversation:

"I had an issue in session 26083761 — can you look up what happened?"

The agent retrieves the last 200 lines of context automatically — no special commands needed.

Installation

Via Marketplace (Recommended)

/plugin marketplace add pcvelz/cc-search-chats-plugin
/plugin install search-chats@cc-search-chats-marketplace

Via Direct URL

/plugin install --source url https://github.com/pcvelz/cc-search-chats-plugin.git

Usage

Just tell Claude what you need. The plugin handles the rest.

Finding Past Sessions

"Find sessions where we discussed API integration"

"Search for CORS issues across all my projects"

"What did we talk about regarding database migrations last week?"

"Look for any session mentioning 502 gateway errors"

/find-chat — identify a past session

Use when you refer to an earlier chat but don't have its session ID:

• "find the last chat where we discussed the staging deploy"
• "which session was the redis bug in?"
• "what did we work on yesterday?" (add "across all projects" to widen)

It returns a short list of candidate sessions (id, date, opening prompt), scoped to the current project by default, then nudges you toward /summarize-chat <id> (recap) or /search-chat <id> (content). It does not print transcript content itself — it's the find step before those.

Recalling a Specific Session

"What did we talk about in session bbfba5e4?"

"Show me session bbfba5e4-c5e7-4464-af03 — I need to pick up where we left off"

"Help me fix the server memory issue I found during session 26083761"

Summarizing a Session

When you want a digest rather than the full transcript:

"Summarize session 38c00401"

"/search-chats:summarize-chat 38c00401" — Haiku summary (default)

"/search-chats:summarize-chat 38c00401 --detailed" — Sonnet, exhaustive recall

"/search-chats:summarize-chat 38c00401 --eu" — Scaleway Devstral (GDPR-safe hedge)

The command extracts the last ~2000 lines of the session to a tmp file and dispatches a summarizer subagent — the transcript never lands in your main context, so you can summarize arbitrarily long sessions cheaply. Model choice backed by an empirical 19-fact-recall benchmark.

Extracting Specific Content

"Show me the last 50 lines from session bbfba5e4"

"Extract session bbfba5e4 and show me only the lines about chrome errors"

"Pull up session e7f2b08c and find the part about the fix for the preflight response"

"Get everything from session bbfba5e4 that mentions error or warning or failed"

Smart Interpretation

The plugin figures out what you mean from context:

What you say	What happens
"Find sessions about CORS policy"	Searches all sessions for CORS-related discussions
"Look up session e7f2b08c"	Tries as session ID first, falls back to text search if no match
"From session e7f2b08c, show me the Allow-Origin lines"	Extracts the session and filters to matching lines
"What was the fix for the preflight response in session e7f2b08c?"	Longer question detected — extracts full session for the agent to interpret
"Search for CORS across all my projects"	Searches every project's chat history, not just the current one

How filtering works: Short references (1-4 words) are used as keyword filters. Longer questions (5+ words) are treated as instructions — the full session is extracted so the agent can interpret it semantically. Session IDs that don't match any session fall back to text search automatically.

Cross-Project Search

"Search for deploy failures across all my projects"