d7e06c3085
The macOS auto-import was failing with "Cursor database not found" even when Cursor was installed and logged in. This was caused by a single hardcoded path and no fallback when the DB file existed but couldn't be opened (e.g. WAL lock, Insiders variant). Changes (macOS only — linux/win32 paths are unchanged): - Probe both standard and Insiders DB locations on macOS - Return a descriptive error when the DB file exists but can't be opened - Try multiple known key names for token and machine ID - Add fuzzy key fallback for future Cursor schema changes - Normalize JSON-encoded string values from the DB Adds unit tests covering all new and existing behavior. Co-authored-by: Cursor <cursoragent@cursor.com> |
||
|---|---|---|
| .. | ||
| app | ||
| lib | ||
| mitm | ||
| models | ||
| shared | ||
| sse | ||
| store | ||
| proxy.js | ||
| server-init.js | ||