"Add symbol to new chat" seems to be blocked on "Show call hierarchy"

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I was using Cursor IDE in a big Python codebase. I called “Show call hierarchy” on a function foo(). As that takes a while, I decided to look at another function bar() while waiting. I tried to call “Add symbol to new chat” on function bar(), but nothing happens. Then, when “Show call hierarchy” for function foo() returns, then immediately a new chat was created with the location for function bar() appears as the context. My guess is “Add symbol to new chat” is blocked on “Show call hierarchy”, which seems unnecessary. Why can’t they be on 2 different threads?

Steps to Reproduce

  • Call “Show call hierarchy” on a function foo(), which takes a while to return (nothing unusual here)
  • Call “Add symbol to new chat” on function bar(), but nothing happens for a long while.

Then, when “Show call hierarchy” for function foo() returns, then immediately a new chat was created with the location for function bar() appears as the context.

Expected Behavior

“Add symbol to new chat” on function bar() should have created a new chat immediately, instead of after “Show call hierarchy” for function foo() finishes.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.35
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120
Date: 2026-01-13T07:39:18.564Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, good report. It looks like these operations really do use the same shared queue for LSP requests.

I’ll pass this to the engineers to review. Your shared thread hypothesis seems plausible. Ideally, “Add symbol to new chat” shouldn’t have to wait for “Show call hierarchy” to finish.