Chat does not return any answer

Hi Cursor team,

I’ve encountered an issue multiple times where I input something into the chat, Cursor processes it, but then nothing happens. The chat input box (to ask a followup) just reappears without any response:

Last week, I recommended Cursor to a colleague. One of the first things he experienced was the same problem: he wrote a prompt, Cursor worked on it, but then the chat input reappeared without an answer.

This has been an issue for quite some time. I hoped it would be fixed in some of the releases, but since nothing has changed, I’m writing to report it.

For me this is the most “bugging” bug in Cursor! When this happens, I often can’t get Cursor to respond at all (followups do not return answers as well…).
I have to start a new chat and sometimes rephrase my prompt to hopefully get a result. Really annoying if I have a lot of context in my chat already -.-
(not even sure if these kind of requests count as fast-requests?)

Also: this kind of silent failure is the worst kind of behavior. An error message with some indication of what went wrong would be much better. Ideally, this issue should of course be fixed so that some kind of answer is always provided :slight_smile:

Here the version, but as mentioned - this has been an issue for me for many versions.

Version: 0.40.1
VSCode Version: 1.91.1
Commit: 58b91712431381a1b75817cd3437cee35dddcb30
Date: 2024-08-24T02:52:24.035Z
Electron: 29.4.0
ElectronBuildId: undefined
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.6.0

1 Like

For reference, I added some, possibly naive, brainstorming around the ‘silent failing’ dynamic in this post, hoping to get a good outcome for all involved etc:

I’m not sure though if the LLM providers count all such requests as successful or not.

I’m not sure where the ‘time out’ (if that’s what it is) occurs, either with the LLM provider response or within Cursor.

1 Like

This has happen to me numerous times as well.

Same for me today.
Before the update, things were smooth.

Version: 0.40.1
VSCode Version: 1.91.1
Commit: 58b91712431381a1b75817cd3437cee35dddcb30
Date: 2024-08-24T02:52:24.035Z
Electron: 29.4.0
ElectronBuildId: undefined
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.19045

Had a similar issue here: Asking questions in chat suddenly takes over 2-3 minutes per question - #2 by truell20

Unfortunately, no response from @truell20 after I provided all the details.

The annoying this about getting no response is that it still consumes credits, so if it happens 3-4 times a day and you retry the same question (which again fails), now you’re losing 10 credits a day for nothing :confused:

Wasn’t sure if that actually counts as one of the fast-requests (never checked). But in that case it is of course even worse of an issue…

One notice: This seems to happen particularly often with the long context mode.

Update: Happens almost every time in long-context mode when adding @codebase - I mean really almost every time…

It just stops at “Gathering chunks using conversation history…”

image

and nothing more happens afterwards.