How to Search Cursor Chat History Across Workspaces
Originally published on Extracurricular AI . You remember fixing the authentication bug. You cannot remember which project contained the conversation. cursor-history searches conversation text in supported local Cursor stores across discovered workspaces. It can read history created before you installed it, without a capture hook, embeddings, or an API key. Start with a phrase you remember npm…
Cursor Chat History can be searched across workspaces using the cursor-history CLI tool. Begin by installing the tool globally with the command `npm install -g cursor-history`. To view all discovered workspaces and sessions, run `cursor-history list --all`. To search within a specific workspace, use `cursor-history --workspace /absolute/path/to/project search "connection pool"`.
This will display up to 10 matching sessions by default. If too many results are returned, narrow the search with a more distinctive substring, like `cursor-history search "ECONNRESET" -n 30`. To view a specific session, use `cursor-history show <session_index>`. The session index is not the same as the search result's ordinal position.
If a search returns no results, try a shorter phrase or an exact error token. For more information on the search algorithm and configuration options, refer to the source material.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
