Agent questions panel file links don't navigate to file/line like chat links do

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In the Agent “Questions” inline UI panel, file references (e.g. mdc:src/GrassSimulation.cpp:45) render as clickable links, but clicking them triggers a Windows “Get an app to open this ‘mdc’ link” dialog instead of opening the file and jumping to the relevant line in the editor.
In chat, the same references render as proper file links (e.g. GrassSimulation.cpp (line 45)) that open the file and jump to the correct line when clicked.
Expected behaviour: Clicking a file link in the Questions panel should open the file and jump to the specified line, the same way chat file links do.

Steps to Reproduce

Use Agent mode and trigger a question that references a specific file and line (e.g. via mdc: links)
Click the file link in the Questions panel
Windows prompts to find an app to handle the mdc: protocol instead of navigating in the editor

Expected Behavior

The IDE should open the mentioned file in a new (or existing) tab and jump to the indicated line.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.8.18 (user setup)
VS Code Extension API: 1.105.1
Commit: 36fd6c05fc9b5e02c44c5416c334ff4e796c4b20
Date: 2026-06-20T06:38:57.798Z
Layout: editor
Build Type: Stable
Release Track: Nightly
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the detailed report. The screenshot and version info are exactly what we need.

I can confirm the bug. In the Agent panel Questions, file links are rendered without the same link handler we use in chat, so clicks on mdc: links aren’t intercepted. On Windows, that falls through to the OS dialog Get an app to open this ‘mdc’ link. In chat, the same links navigate correctly because the handler is attached there.

I’ve reported this internally. I can’t share a fix timeline yet, but I’ll post an update in the thread once I have one. As a temporary workaround, open the file and line using the links in the chat itself. Those work as expected.

Thanks for the quick response and for the suggested workaround, which I have already been using in the meantime.