Cursor 3 upgrade breaks the "Fix in Cursor" Cursor Bot links

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

BugBot

Describe the Bug

I upgraded to Cursor 3 this morning (v3.0.12). Created a new Github PR. Bugbot ran as normal and reported an issue. Clicking the “Fix in Cursor” button, as I have done many times in the past. After redirect to Cursor, I’m now greets me with an error dialog. The dialog has the following text and an OK button:

Workspace Not Found
This link is for <repo_author>/<repo_name>, but Cursor doesn’t have a local workspace open for that repository yet.
Add this repository from the sidebar, then try the link again.

The workspace I have open is for that repository. Not sure what “adding repository from the sidebar” means.

I tried a few different things, including moving the directory, doing a fresh checkout, creating a .code-workspace file. The error persists.

Steps to Reproduce

  • Open a GIthub PR that triggers a Bugbot comment.
  • Click “Fix in Cursor” button from a Bugbot comment in a Github PR.
  • Browser redirects to Cursor, a dialog pops up

Operating System

MacOS

Version Information

Version: 3.0.12
VSCode Version: 1.105.1
Commit: a80ff7dfcaa45d7750f6e30be457261379c29b00
Date: 2026-04-04T00:13:18.452Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

Hey, thanks for the report. This is a known issue with BugBot deeplinks. After an update, the Fix in Cursor link handler doesn’t always correctly find an already open workspace.

The team is aware, but there’s no ETA for a fix yet. Your report helps with prioritization.

As a workaround, make sure the window with the right repo is the only Cursor window open close the others and then click the link again.

Let me know if that helps.

6

Thanks for the update. This makes working on parallel tasks much more difficult. For now I’m copying and pasting the bugbot report into Cursor as a workaround. Closing other windows is not a super practical solution and will affect token usage for you guys. :wink:

1 Like