Hey, thanks for the detailed report. There are two separate issues here, so let’s go one by one.
- Login doesn’t get picked up in the IDE.
On Linux, the login flow works differently than on macOS. There’s nocursor://redirect back into the app. The browser stays on the confirmation page, and the IDE picks up the session in the background via polling. The most common reason this gets stuck is the default Electron settingHttp: Proxy Support = override, which can silently block the polling requests.
Try this:
- Open Settings
Ctrl+, - Search for
Http: Proxy Support - Change
overridetoon - Restart Cursor and sign in again using the Log In button inside the app. Manually opening the login page won’t link the session to the IDE. You need the built-in flow with challenge/uuid.
If you’re using a proxy via env vars, that can also break it. Check:
env | grep -i proxy
Then run Cursor without them:
env -u http_proxy -u https_proxy -u HTTP_PROXY -u HTTPS_PROXY -u all_proxy cursor
Same fix helped in similar threads:
- KDE Discover opens instead of Firefox.
Ifxdg-open https://cursor.comopens Firefox in a terminal, that still doesn’t mean the AppImage sees the same MIME defaults in its environment. Check the default handler for the scheme:
xdg-mime query default x-scheme-handler/https
xdg-mime query default x-scheme-handler/http
If it’s not Firefox, set it explicitly:
xdg-mime default firefox.desktop x-scheme-handler/https x-scheme-handler/http
Also check ~/.config/mimeapps.list. There shouldn’t be a mapping that points x-scheme-handler/https to Discover. This is a KDE and AppImage environment behavior, not a Cursor-specific one.
Let me know how it goes. If login still doesn’t get picked up, open Help > Toggle Developer Tools > Console during the login attempt and share the red errors, and we’ll dig deeper.