Cursor Took Over My 250GB Storage Without Noticing WTF

By SwiftEcho377 · ISSUE · About Cursor

I kept getting error messages that I got no storage spaces in my Mac. Application Support had 300GB unknown files turns out Cursor kept saving snapshots - the worst part is, I didn’t even use Composer nor cursor chat box, just a terminal in cursor and I was just working with Claude Code. Cursor, why are you sneak peaking and taking snapshots wtf. I disabled it now, but I am afraid such things are happening anyways. Does move back to VSC help here? Or same thing on the other side?

54 upvotes · 5 comments

Comments (5)

ZenPanda516: This reeks of you not using git. stop being silly with your vibecoding and, while you wait, learn about proper coding setups

CrystalScout894: Wait till you find out your Docker builds is a nice 300000000 gigs cuz it never deletes its tons of failed builds.

SarahKim: ran into the exact same thing. I build native macOS apps and between Cursor snapshots, Xcode derived data, and docker layers my 1TB drive was somehow at 95%. the fix for me was adding a weekly launchd job that nukes ~/Library/Application Support/Cursothis community/History and the derived data folde

CrystalScout894: Y'all good here? The fuck?

AlexChen: oh man this happened to me too. 249 GB of snapshots is insane. the fix is exactly what you found but id also add that if youre building a project with Claude Code you can specify in your [CLAUDE.md](http://CLAUDE.md) to not create unnecessary snapshot triggers. also worth periodically running a clea

More discussions about Cursor on HonestUse