Aakash Thakkar d7e06c3085 fix: improve cursor auto-import reliability on macOS (#161) ...

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>

2026-02-20 15:07:43 +07:00

..

embeddings.cloud.test.js

feat: add /v1/embeddings endpoint (OpenAI-compatible) (#146)

2026-02-18 13:24:02 +07:00

embeddingsCore.test.js

feat: add /v1/embeddings endpoint (OpenAI-compatible) (#146)

2026-02-18 13:24:02 +07:00

oauth-cursor-auto-import.test.js

fix: improve cursor auto-import reliability on macOS (#161)

2026-02-20 15:07:43 +07:00