Chat/Composer no result

I’m a pro user. It has worked well for a few months. And since a few days ago it has no response.

I asked a question as usual, and then it showed a blinking ‘…’ for about one second and then disappeared, and then… nothing come out (my question was still there, just no answer).

I have tried various AI models for several days and still have the same condition.

Any suggestions? Thanks.

Version: 0.45.11
VSCode Version: 1.96.2
Commit: f5f18731406b73244e0558ee7716d77c8096d150
Date: 2025-02-07T09:43:58.555Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.26100

Hey, does this also happen in a new Chat/Composer session?

Yes, also for new chat/composer sessions.

Dean Rie via Cursor - Community Forum <[email protected]> 於 2025年2月13日 週四 18:53 寫道:

Can you check if there are any errors in the DevTools panel?

No errors displayed.

Try clearing the cache by following this guide. If that doesn’t help, try reinstalling Cursor:

The linking page doesn’t exist. 404 error.

By the way, I just tried to logout and then login. It showed login successfully on browser, but not on the Cursor editor. Is there anything related to my chat/composer failure?

I’m not exactly sure, since you mentioned that no errors are showing, I also changed the link to a similar article.

OK. Thanks. Since it’s late here, I’ll try it and come back tomorrow.

I have uninstalled the Cursor app, cleaned related files, and re-installed the app.

At the app login, it brought the browser to login at Cursor site. I logged in and confirmed it successful with my subscription information there. But the problem is this login did not change the app’s status (not login in the app).

I don’t know why this happened but I guess this was the reason Chat/Composer had no response.

BTW, I tried my other windows apps that also need the browser login. They worked fine.

For the sign in / login problem, I have tried firewall disabled and various default browsers, but could not solve the problem.

This definitely sounds like a sign-in sync issue between the browser and Cursor. Let’s try completely signing out:

  1. Open Cursor’s command palette (Ctrl/Cmd + Shift + P)
  2. Go to Cursor Settings > General tab
  3. Click Sign Out if the option is there
  4. Close Cursor completely
  5. Reopen and try signing in again

If that doesn’t work, you can try manually clearing the auth data:

  1. Close Cursor
  2. Delete the folder:
    • Windows: %APPDATA%/cursor/User
    • Mac: ~/Library/Application Support/cursor/User
  3. Reopen and try signing in

If neither work, let me know where things get stuck!

Thank you for your help, but both methods failed.

The first one is to sign out and sign in. But since 10 days ago, I already could not sign in anymore.

The second method. I actually did the similar earlier after surfing the solution on the forum. Anyway, I tried it again…

Regarding the deleting folder, do you mean
C:\Users\User\AppData\Roaming\Cursor\User

I deleted this file and reopen the Cursor. It went to login option on the Cursor:

Pressed the Log In button, it went to the browser login:

Pressed “Yes, log in”, the browser screen change to

BUT, the Cursor App remained the same…

When this happens, do you see any errors in the browsers developer tools?

The console of the devtools was clean, nothing appeared.
However, there were two issues:

The violating node is on the language selection at the bottom of the page.

Dan via Cursor - Community Forum <[email protected]> 於 2025年2月26日 週三 上午6:59寫道:

That shouldn’t be an issue here. When you hit log in, does Cursor open if it was closed at that point?

No. Interestingly, I had tested that before. At that time, if I open devtools panel, it will open Cursor app, but if devtools not opened, the app won’t open.

I installed ver. 0.45.15 the other day (previously 0.45.11). Now hitting login on browser won’t open Cursor app (if it was closed) in any case.

I checked my previous test notes. Previously, after I hit the login button on browser, if I had opened the devtools panel, I ccould see
Launched external handler for ‘cursor://’
on the console.
But not now.