Xdg-open cursor:// runs agent

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

xdg-open seems to be working incorrectly possibly being the problem behind mcp oauth login not working in cursor on linux.

Steps to Reproduce

Install cursor from deb
Run dummy command like “xdg-open cursor://some-command”
The response will be json messages from the agent instead of this being sent to IDE

Expected Behavior

xdg open of cursor urls should be handled by the ide to allow oauth callback delivery.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.17
VSCode Version: 1.99.3
Commit: 34881053400013f38e2354f1479c88c9067039a0
Date: 2025-09-29T03:10:26.099Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Linux x64 6.14.0-32-generic

hi @mkschreder can it be that this is related to our new deeplink feature?

Not sure. Hard to tell. I think it is probably related though to bundling of cursor-agent with cursor install because now running “cursor” in terminal doesn’t start the ide but rather runs something else that chooses whether to run agent or ide. I think xdg-open probably expects that running “cursor” with a cursor url will send that url to cursor based on the install bindings but the executable instead routs it to the agent.

1 Like

In 1.7.28 it now opens a new cursor window but thinks it’s a file to be edited. So it opens a file with the full response code url as name.

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.