What Cursor's 8GB Storage Bloat Teaches Us About Claude Code's Clean Architecture

A deep dive into Cursor's scattered 8GB local storage reveals why Claude Code's ~/.claude/projects/*.jsonl approach is better for developers. The Storage Audit That Revealed Cursor's Complexity A developer's forensic analysis of Cursor's local storage reveals a sprawling 8GB footprint spread across multiple locations: ~/.cursor/, Application Support folders, and a massive 1.2GB SQLite database called state.vscdb. This isn't just cache—it's a complex system with chat databases, transcript files, global state blobs, and workspace tracking. Run this command on macOS to see your own Cursor footprint: du -sh ~/.cursor ~/Library/Application\ Support/Cursor 2>/dev/null The analysis found three primary storage layers: SQLite chat databases (~/.cursor/chats/*/*/store.db) - 280MB across 171 files Transcript JSONL files (~/.cursor/projects/*/agent-transcripts/*.jsonl) - 138 files with conversation text Global state database (~/Library/Application Support/Cursor/User/globalStorage/state.vscdb)