How do I export chat with AI?

I bought and I tried. It doesn’t work.

See this screenshot. CleanShot 2025-01-21 at 11.34.35 · CleanShot Cloud i got command ‘cursor-convo-export.exportChat’ not found. Restarted cursor same thing.

I would like a refund if cannot fix.

Thank you

2 Likes

Update 2025-01-22 11:59: I released version 1.0.1 this morning, which should fix this. I’ve sent you an email and you can check the Gumroad page).

  • Edwin

Hey @simkimsia, thanks for buying and reaching out.

I’m checking this problem (had 3 people with same issue) and will provide a fix if possible. Are you using the Mac or Windows version of Cursor?

If no fix can be applied you will get a refund.

I’ll keep you posted by the email you purchased with.
Thanks again and I’ll get back to you soon,

Edwin - maker of the Cursor Convo Export extension

Hey there, finally got this working for everyone, version 1.0.3 fixes the command not found issue. It is available at the product site. Happy exporting!

1 Like

I can recommend SpecStory, the export is automatic and timely. Worked better than most manual or hacked solutions. the benefit is you can reference it then in another chat as file with @

2 Likes

ok it works. thank you

2 Likes

There should be a way to automatically log all sessions to a logging folder.

1 Like

Introducing cursor-export:
Your solution to download & backup Cursor chat history!

Export all your valuable conversations to Markdown/HTML/JSON.
Never lose those brilliant coding solutions again!

It’s FREE and open-sourced.


Just run(replace {scott} with your username):

npx cursor-export --workspacePath="/Users/scott/Library/Application Support/Cursor/User/workspaceStorage"

Now is 2025.3.9

true

I’d like to expand on this feature request with a focus on automated logging and time management.

Proposed Automated Solution

  1. Real-time Auto-logging
  • Instant save without manual intervention
  • Configurable save location
  • Minimal performance impact
  • Preserved formatting (especially code blocks)
  1. Time Management
  • Default UTC+8 timezone support
  • Project-specific timezone settings
  • Precise timestamps (millisecond level)
  • Multi-timezone display for global teams
  1. File Structure
    Default naming pattern:
    YYYY-MM-DD_HH-mm-ss_[ProjectName]_chat.md

Example content:

# Project: MyApp
Created: 2024-03-14 15:30:00 UTC+8

[2024-03-14 15:30:45.123 UTC+8] User
Question about implementation...

[2024-03-14 15:30:47.456 UTC+8] Assistant
Here's the solution...

# Time References
- UTC: 2024-03-14 07:30:45.123
- Local: 2024-03-14 15:30:45.123
  1. Team Features
  • Easy sharing with team members
  • Multi-user annotations
  • Git integration
  • Cross-timezone collaboration

This would solve the main issues mentioned in this thread:

  • No more manual copying
  • Preserved formatting
  • Easy sharing
  • Accurate time tracking
  • Development workflow integration

Would love to see this implemented!