How to View Your Cursor Conversation History: A Complete Guide
Cursor has become one of the most popular AI coding editors, with millions of developers relying on it daily. But a common frustration keeps coming up: how do you find and view your past Cursor conversations?
Whether you're looking for a code snippet from last week, trying to recall how you solved a tricky bug, or wanting to export conversations for documentation, this guide covers every method available.
Method 1: Cursor's Built-in History
Cursor provides a basic history feature that's easy to miss.
Accessing Chat History
- History Button: Look for the "Show History" button in the Agent panel sidebar
- Command Palette: Press
Cmd+Shift+P(macOS) orCtrl+Shift+P(Windows/Linux) and type "Show Chat History" - Background Agents: Use
Ctrl+Eto view background agent chats, which are stored separately from regular history
Limitations
- History is stored locally only — it's tied to your machine, not your Cursor account
- No search across conversations
- No export functionality
- Background agent conversations are stored in a remote database, separate from local history
- If you reinstall Cursor or switch machines, your history is gone
Method 2: Finding the Raw Data Files
Cursor stores conversations in SQLite databases on your local filesystem:
| Platform | Path |
|---|---|
| macOS | ~/Library/Application Support/Cursor/User/ |
| Linux | ~/.config/Cursor/User/ |
| Windows | %APPDATA%\Cursor\User\ |
The chat data lives in .vscdb files. You can query them directly using SQLite tools:
# Using datasette to browse the database
datasette state.vscdb
# Then visit http://localhost:8001 and query:
# SELECT rowid, [key], value FROM ItemTable
# WHERE [key] IN ('aiService.prompts', 'workbench.panel.aichat.view.aichat.chatdata')Caveat: This is a manual, technical process. The data is stored as JSON blobs inside SQLite tables, making it hard to read without additional tooling.
Method 3: VS Code Extensions
CursorChat Downloader
A VS Code extension that lets you view and browse Cursor AI chat history directly in VS Code:
- Access conversations across all your Cursor workspaces in one place
- View complete chat history including AI responses with model details
- Available on the VS Code Marketplace
Cursor Chronicle
A CLI tool for advanced history management:
- Search across all your chat history
- Export conversations to Markdown
- View stats (messages, tokens, tool calls, activity by project)
- Browse dialogs by date or project
- Pure Python with zero dependencies
Method 4: Dedicated History Viewers
Cursor View
An open-source local tool that provides:
- Search and browsing across your entire Cursor chat history
- Export conversations in readable formats
- Works by scanning Cursor's application data directories and extracting data from SQLite databases
Method 5: Unified Session Management with Mantra
All the methods above share a key limitation: they only handle Cursor conversations. If you also use Claude Code, Gemini, or other AI tools, you need separate solutions for each.
Mantra takes a different approach by unifying all your AI coding sessions in one place:
- Automatic import: Mantra's import wizard detects your Cursor sessions and imports them alongside Claude Code and Gemini sessions
- Visual timeline: Browse through conversations with a scrubable timeline — no SQL queries needed
- Full-text search: Search across all sessions from all tools simultaneously
- Time travel: Navigate to any point in any session and see the complete context
- Content filtering: Focus on specific message types — code changes, explanations, or tool calls
- Local-first: Everything runs on your machine. Your conversation data stays private
Getting Started
- Download Mantra for macOS, Windows, or Linux
- Launch and open the Import Wizard
- Mantra automatically scans for Cursor sessions in the standard data directories
- Import and start browsing your conversation history visually
Comparison: Which Method Is Right for You?
| Method | Ease of Use | Search | Export | Multi-Tool | Privacy |
|---|---|---|---|---|---|
| Built-in History | High | Limited | No | No | Local |
| Raw SQLite | Low | Manual | Manual | No | Local |
| VS Code Extensions | Medium | Yes | Some | No | Local |
| Cursor View | Medium | Yes | Yes | No | Local |
| Mantra | High | Full | Yes | Yes | Local |
Tips for Managing Your Cursor History
- Back up your data directory regularly if you rely on Cursor's local storage
- Use
@Past Chatsin Cursor to include context from previous conversations in your current chat - Tag important conversations mentally or in a separate notes file — Cursor doesn't have a favorites feature
- Consider a unified tool if you use multiple AI coding assistants — maintaining separate workflows for each tool creates unnecessary friction
Conclusion
Accessing your Cursor conversation history doesn't have to be a scavenger hunt through SQLite databases. Whether you use Cursor's built-in features, a dedicated extension, or a unified tool like Mantra, the important thing is having a reliable way to access your past AI interactions.
As AI-assisted coding becomes the norm, treating your conversation history as a valuable knowledge base — not disposable chat logs — will give you a significant advantage in maintaining context and building on past work.
Want to unify all your AI coding sessions? Try Mantra — import Cursor, Claude Code, and Gemini sessions into a single visual timeline.
Read more:
- Cursor Session History Alternatives — Compare all your options for accessing Cursor history
- AI Coding Session Replay: Why You Need a Time Machine
- Claude Code Session Replay Tools — If you also use Claude Code
- AI Coding Session Manager Alternatives — Full overview of session management approaches
- Quick Start Guide
- Import Wizard Documentation