-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
An earlier build generated a wrapper .app per profile. Removed, because:
- It didn't work while running — macOS shows the icon of whatever bundle is actually executing, so open windows always showed Cursor's stock icon.
- It multiplied permission prompts — each wrapper is a distinct app identity, and macOS ties Microphone/Camera/folder consent to whichever bundle launched Cursor.
Per-profile title bar colors replace it (a JSON settings edit — no new app
identity). Windows instead offers .lnk taskbar shortcuts, which dodge the
identity problem because they point at the same Cursor.exe.
No. Everything is local: process lists, the on-screen window list, and
files under ~/.cursor_profiles. No network code, no analytics, no daemon.
(The npm/pip installers download the release binary once, from GitHub.)
System CPU % comes from kernel deltas, which need two samples — the first poll has nothing to diff against, so a dash shows until the second one lands (about one poll interval).
Wayland exposes no global window list to clients. The GUI apps count on-screen windows where the OS allows it; the TUI shows PIDs and live memory instead of a guessed number.