CMD+K + @Documenation triggers "Cannot access 'U' before initialization" and breaks entire app (0.43.4)

I keep getting this after trying to @ mention docs using cmd+k. It breaks every single composer/chat/cmd+k etc after that until a restart. Basically breaks most (or all) custom cursor-related elements of the IDE.

  • Chats show as blank.

  • CMD+K menu is frozen.

  • if CMD+k is open in a new window, typing in that types in the entire editor

  • All cursor-related inputs are broken.

  • the tell, when bug is freshly triggered – completion just hangs with one dot (the loading dot dot dot)

Version: 0.43.4

VSCode Version: 1.93.1

Commit: 48d735e3dec42accfdf71efabf00bb49e242b880

Date: 2024-11-26T00:13:53.586Z (1 day ago)

5 Likes

Can confirm this behavior on 0.43.5 on Linux as well.

+1 Also on OSX, I triggered it from the inline editor.

1 Like

I am experiencing this on 0.43.5 as well on Windows. This issue was not occurring until I updated to 0.43.5 this afternoon.

Same issue:

  • OSX 14.1.2 (23B92)
  • Cursor Version: 0.43.5
  • VSCode Version: 1.93.1

All the same behaviour as asherhunt + strange unexpected behaviours with the editor.

Hey all,

Sorry about this - I’ve raised it internally to look into!

Has anyone been able to reproduce this after a certain set of events, and does this happen only when trying to add (@) context, or is it somewhat random?

If you find any pattern to it, that may help us track this down.

Thanks

I can confirm i have the same bug as described by @asherhunt on 0.43.5
When I open Cursor, if I first only ask a question on the Chat with or without @ docs, works fine. Also, if after that, i open the inline chat and ask it something without @docs, either as direct modification or quick question, it works fine.
The bug breaks everything only when i specifically add a @docs element in the inline chat, either for code modification or quick question. Then the inline chat becomes unresponsive, as well as the normal Chat, i can’t select my models anymore, the settings don’t work, and i need to reboot the app completely to get back to interacting with an LLM.

Hello,
I have exactly the same problem. It is really painful… Do you have any updates for a fix please ? @danperks

Hi,

We are aware of this issue and are currently working on a fix.
Sorry for the issues it may be causing with your use of Cursor!