Marketplace for CC Search Chats plugin
npx claudepluginhub pcvelz/cc-search-chats-pluginSearch and extract Claude Code chat history with keyword matching, session extraction, and local LLM analysis
pcvelzA Claude Code plugin for searching and extracting chat history from previous sessions.
/plugin marketplace add pcvelz/cc-search-chats-plugin
/plugin install search-chats@cc-search-chats-marketplace
/plugin install --source url https://github.com/pcvelz/cc-search-chats-plugin.git
/search-chat "keyword"
/search-chat "API integration" --limit 5
/search-chat <session-uuid> # auto-detects UUID, extracts full session
/search-chat bbfba5e4 # partial UUID (first 8 chars) — resolves automatically
/search-chat bbfba5e4-c5e7-4464-af03 # truncated UUID — also resolved via prefix match
/search-chat bbfba5e4 chrome errors # UUID + filter — extract session, show matching lines only
/search-chat bbfba5e4 error --context 3 # UUID + filter with 3 messages of context
/search-chat bbfba5e4 --tail 50 # last 50 lines of session
/search-chat --extract <session-id> # explicit extract (same result)
/search-chat "staging" --extract-matches
The plugin automatically interprets your input:
| Input | Interpretation |
|---|---|
"CORS policy" | Search for sessions mentioning CORS issues |
e7f2b08c | Try as session UUID → if no match, search as text |
e7f2b08c "Allow-Origin" | Extract session, grep for lines about the missing header |
e7f2b08c "what was the fix for the preflight response" | Instruction detected (>4 words) — extracts full session for LLM interpretation |
e7f2b08c-4a91-43d6-8c5e-... | Full UUID — extracts the session directly |
--extract e7f2b08c | Explicit extract (errors if session not found) |
"CORS" --all-projects | Find CORS issues across all your projects |
How filtering works: Short text (1-4 words) is used as a grep keyword. Longer text (5+ words) is treated as an instruction — the full session is extracted so the LLM can interpret it semantically. Auto-detected UUIDs that don't match any session fall back to text search. Explicit --extract still errors when not found.
/search-chat "CORS" --all-projects # find CORS issues across all projects
/search-chat "502 gateway" --all-projects # find gateway errors everywhere
/search-chat "CORS" --project /path/to/project # search specific other project
| Option | Description | Default |
|---|---|---|
--limit N | Maximum sessions to return | 10 |
--project PATH | Search in specific project | current |
--all-projects | Search across all projects | current only |
--extract ID | Extract specific session | - |
--extract-matches | Auto-extract top matches | false |
--extract-limit N | Number to extract | 5 |
--max-lines N | Max lines per extraction | 500 |
--context N | Messages of context around filter matches | 0 |
--tail N | Show only last N lines of extraction | - |
--include-agents | Include subagent conversations in search/extraction | off |
--include-self | Include current session in results (excluded by default) | off |
--exclude-session ID | Exclude a specific session by ID | - |
[TOOL:name] without paths, commands, or inputs, preventing LLMs from acting on historical tool invocations▏ to visually mark content as archived transcript[ARCHIVED] reminder inserted every 50 lines to reinforce read-only status throughout long extractions