Feature request for product/service Cursor IDE Describe the request As a software engineer frequently balancing multiple projects simultaneously, I often have several Cursor windows open at once. Currently, the chat history and Composer sessions are isolated to their respective windows, which creat…

Hey, thanks for the feature request. Right now, chat history is actually isolated per workspace. Each Cursor window keeps its own history separately. Similar requests have already come up: Allow smart searching through conversation history Chat History Search & Branching Conversations I’ll pass …

Thanks @deanrie for your prompt reply. I hope these features make it to prod some day.

Check Chat Wizard - a VS Code extension (also available at Open VSX Marketplace ) that supports Cursor - and provides searching capabilities across all chats, among other functionalities, such as injecting chat as context into a new conversation. Have been doing the job for me ever since.

Same pain here, I had chats spread over maybe 15 projects and no way to find the one where I’d figured out a build issue. What I ended up doing: the chats are just files. On older builds it’s all in state.vscdb under globalStorage, newer builds write jsonl transcripts into ~/.cursor/projects/. Noth…

Hey, thanks for sharing workarounds in the thread. For users who need a fix right now, that’s helpful. Quick note: deja, Chat Wizard, and similar tools are community-made, not ours, and they read local history files directly (state.vscdb / jsonl transcripts). They run locally, but please use them at…

Fair point on the backup, thanks. For what it’s worth deja opens state.vscdb read-only (sqlite3 -readonly, and immutable=1 when Cursor isn’t running) and never writes to the Cursor folder, the index lives in its own cache dir. But yes, a copy of the folder before trying any of these tools costs noth…

For the “I remember the fix, but not which workspace it happened in” part, I have also found that very incovienient myself, so I built and maintained cursor-history, and its now a battle tested tool that have steady downloads and users, I am even looking to get cursor official’s support on this proj…

The local search I posted above is meant for that “which project did we solve this in?” problem: you can search a remembered error or function name without opening each workspace. I maintain cursor-history. Its reader covers supported legacy Composer state.vscdb data, Agent JSONL transcripts, and n…

Hey, thanks for the workaround, @borui_cai . Same disclaimer as with deja and Chat Wizard above. cursor-history is community-made, not our tool. It reads local history files directly state.vscdb / jsonl transcripts / store.db. It runs locally, but please use it at your own risk and back up your histo…

Create a unified chat history view across all projects

Ideas Feature Requests

Josh_Mendelsohn (Josh Mendelsohn) February 25, 2026, 7:58pm 5

I second this, posted my own similar request at Sync Cursor chats across workspaces .

Topic		Replies	Views
Chat history folder Help	20	32893	September 9, 2026
Retain context across devices for the account Feature Requests context	2	58	August 11, 2026
Sync Cursor chats across workspaces Feature Requests chat , ssh , large-codebases	4	1465	April 9, 2026
Local IDE agent chats and the Agent CLI still use separate session stores Feature Requests chat , cli , cursor-sdk	3	201	August 31, 2026
Make Project Chats and Context Portable (Store Them with the Project) Feature Requests chat , context	1	60	September 2, 2026

Create a unified chat history view across all projects

Related topics