Account boundary: inseparable: desktop credentials, chat state, SQLite global storage, and singleton behavior have no proven narrow split.
Cursor accepts VS Code-style user-data flags, but per adapter.json those flags do not prove separate desktop auth with shared conversations. The account-overlay contract is therefore not claimed.
Binary discovery: %LOCALAPPDATA%\Programs\cursor\Cursor.exe (Windows), /Applications/Cursor.app (macOS), /usr/bin/cursor or /opt/Cursor/cursor (Linux).
Use a whole-root profile for Cursor Desktop:
multi-cli new cursor/work --isolated
multi-cli launch cursor/workFor a process-token boundary, use the Cursor CLI adapter (cursor-cli).
- Mechanism:
inseparable: credentials, chat databases, and global storage are not proven separable. - Logout scope: user.
- Concurrency: single instance per OS user (
singletonScope: user).
None claimed. adapter.json declares no shared, session, or file paths under the native root (%USERPROFILE%\.cursor on Windows, ~/.cursor on macOS/Linux).
- Chat history lives in SQLite keyed to workspace state and cannot be portably shared or copied between profiles.
- A narrower boundary requires proof that auth, chat databases, and single-instance behavior are separable; until then nothing is shared.
| Windows | macOS | Linux |
|---|---|---|
supported (--isolated) |
supported (--isolated) |
supported (--isolated) |