Installed extension's `onUri` handler is not invoked for custom URI

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor 3.14.7 logs a custom extension URI as handled, but does not load the installed extension into the extension host or invoke its onUri handler.

Steps to Reproduce

  1. Install coder.coder-remote 1.15.2.
  2. Start Cursor 3.14.7 on Linux with a clean HOME and the standard ~/.cursor/extensions directory.
  3. Open cursor://coder.coder-remote/open?workspace=test&url=https://coder.example.com.
  4. Repeat after Cursor finishes initialization.

Expected Behavior

Observed

renderer.log records the URI as handled, but extension-host initialization does not include coder.coder-remote, and there is no activation or URI-handler entry. On repeat, Cursor invokes workbench.extensions.installExtension even though the extension is installed.

Expected

Load the installed extension and invoke its registered onUri handler.

Operating System

Linux

Version Information

  • Cursor 3.14.7
  • VS Code 1.128.0
  • Commit a758f2241ca99fecf380180b6cbdbbce0f1f42c0
  • coder.coder-remote 1.15.2

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the report. This is a known issue in 3.14.7. cursor:// links for third party extensions can be handled in the Agents window, where the extension doesn’t load, so onUri doesn’t fire.

Workaround:

  • Before opening cursor://coder.coder-remote/..., make a normal IDE window active, not the Agents window. If a fresh profile opens only the Agents window, open a new editor window, then click the link again. In this mode, onUri should work normally.

A fix is already prepared and will ship in the next stable update. I’ll reply here when the update is available. Let me know if the workaround helps.