Thank you for all your replies.
So I put my question to deepseek and gpt, they suggested looking at the state.vscdb file with DB Browser for SQLite. So I opened my current state.vscdb file and sent a screenshot off to gpt and deepseek and they both flagged the cursorDiskKV table as a red flag.
deepseek:
Potential Issue Summary:
The state.vscdb file shows schema corruption (invalid SQL syntax) and an unexpected table cursorDiskXY, indicating possible database corruption or unintended modifications. Combined with prior extreme bloat (1.5 GB), this suggests:
- Cursor/Extension Bug: Faulty logic writing invalid data.
- File Corruption: From crashes or incomplete writes.
- Misbehaving Extension: Creating non-standard tables or spamming entries.
Action: Report the schema anomalies to Cursor’s support team for investigation.
I don’t have the expertise to say how accurate this is, but it’s intresting that both gpt and deepseek pointed out the same cursorDiskXY as being a red flag!