Agent chats not opening after update – constant ConnectError: [unauthenticated] and full_stripe_profile 401 errors

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Describe the Bug, Steps to Reproduce, Expected Behavior.

Describe the Bug
After the latest Cursor update, I can see my existing Agent chats in the sidebar, but when I click on them they never open or load.
In the Developer Tools console I continuously get errors such as:

ConnectError: [unauthenticated] Error

Repeated requests to https://api2.cursor.sh/auth/full_stripe_profile returning 401

https://api2.cursor.sh/auth/poll?… returning 404

ConnectError: [unauthenticated] You must be a team member to access this resource when calling getTeamCommands / availableModels.

Because of this, Agent chat history does not load and Agent mode is basically unusable.
​

Steps to Reproduce

Open Cursor IDE on Windows.

Open the Agent chats panel.

Click on any existing Agent chat in the list.

Observe that the chat never loads and no messages are rendered.

Open Help → Toggle Developer Tools and check the Console and Network tabs.

Notice the repeated ConnectError: [unauthenticated] plus 401 and 404 responses from api2.cursor.sh auth endpoints (full_stripe_profile, auth/poll, team commands, etc.).
​

Expected Behavior

Agent chats should open normally and display their full message history.
If my authentication/session or team access is invalid, Cursor should show a clear error message or re-auth flow instead of leaving Agent chats stuck on loading and spamming unauthenticated errors in the console.
​

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34 (user setup)
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

Yes - Cursor is unusable

Cursor 2.3.34 cannot work on Mac
2

Hey, it looks like this may be a query related to your account billing - if so, the forum is not the best place for this query.

Please drop an email to [email protected] if you have any billing issues.

If you have already sent an email, please be patient - one of the team will get back to you soon!

3

Hi,

Thanks for posting on the Cursor forum!

To help ensure most of our users can participate in discussions, this forum is currently English only.

If you’d like, you can edit your post to translate it into English. Once it meets our guidelines, it will be automatically relisted.

Thanks for understanding!

Note: This is an automated detection system and sometimes makes mistakes. If your post is already in English, feel free to ignore this message, or just make a small edit and it will be reviewed again.

7

This is not a billing issue.

I can successfully create new Agent chats and use them without any problem.
However, all of my older Agent chats that were created before the latest update are still visible in the sidebar, but when I click on them they never open or load any messages.

So billing and general access seem fine – the problem only affects existing/old Agent chat threads, which are stuck on loading and show the ConnectError: [unauthenticated] / full_stripe_profile 401 errors in the console as described above.​

14

Support? It’s an urgent matter, you need to find a solution to this problem. Don’t you know how to read? We can’t downgrade the version, the cursor is stuck??

15

Can someone please tell me why I can’t see the chat that should be in my local machine?! Where is support?

16

Hey, thanks for the report.

This is a known issue. After an update, old chats may fail to load due to auth errors, even though new chats work fine. The team is aware and is working on a fix.

Try this workaround:

  • Cursor Settings (gear icon) → Sign Out
  • Restart Cursor
  • Sign in again

If that doesn’t help, you can try restoring the history manually:

Windows: %APPDATA%\Cursor\User\workspaceStorage\
Find your project folder, open state.vscdb with DB Browser for SQLite, and look for keys like workbench.panel.aichat.view.... Or check ~/.cursor/projects/<project_name>/agent-transcripts, there may be .txt files with your chat history.

Full recovery guide: How to extract full chat history from workstorage - #2 by deanrie

For the future, I’d recommend the SpecStory extension for automatic chat backups.

Can you share a screenshot of the Network tab in Developer Tools when you try to open an old chat? That’ll help us see what’s failing with a 401 error.

17

image
image1898×599 43.5 KB

The error at the very bottom is the one that appears every time I click on a chat.

18

Thanks for the screenshot. The No composer data handle found error happens when you click an old chat. Let’s go through all the steps:

Step 1 - Reset auth:

  1. Cursor Settings (gear icon) → Sign Out
  2. Fully close Cursor (make sure the process isn’t still running in Task Manager)
  3. Open Cursor and sign in again
  4. Try opening the old chat

If that didn’t help - Step 2 - Network diagnostics:

  1. Help → Toggle Developer Tools → Network tab
  2. Click the old chat
  3. Look for red lines (failed requests) to api2.cursor.sh
  4. Click a request and screenshot the Headers tab

If you need the history ASAP - Step 3 - Manual recovery:
Full guide: How to extract full chat history from workstorage - #2 by deanrie

This is a known issue after an update, and the team is working on a fix. Let me know what happens after Step 1.

19

I’ve tried logging out and logging back in multiple times, but it doesn’t work. It doesn’t give any errors when I try to access old chats on the network either. The only thing that happens is this in the logs every time I click on a chat:

workbench.desktop.main.js:13854 [composer] No composer data handle found [handleDeselectingComposer]

Also, requests are constantly being sent to the network and my information is arriving without any errors… But the chat still won’t open?

image
image854×523 19.8 KB

1 Like
20

Thanks for the extra info. I can see all requests are returning 200 OK, so auth looks fine. The issue is with the local chat data.

The [composer] No composer data handle found error means the composer checkpoint data for those chats got corrupted during the post-update migration. Unfortunately, those specific chats can’t be recovered via the UI, this is a known limitation.

But the history is most likely still on disk. Try the manual recovery steps I shared above.

New chats work normally. The problem only affects older chats created before the update.

21

I need to continue the conversation from the old chats. Even if I can retrieve them from SQL Lite, I won’t be able to properly assign them to the new chat; the AI ​​won’t read them all.

22

I understand the issue. Unfortunately, Cursor doesn’t have a chat import feature. Export only works one way.

Ways to restore context:

  1. Extract the history and attach it as a file:

    • Restore the chat from SQLite into a .md file (using the instructions above)
    • In a new chat, use @Files and attach that .md file
    • The AI can read the history as a context document

  2. Copy the key parts manually:

    • Open the restored .md file
    • Copy the most important context into the first message of the new chat

Attaching the .md file via @Files should give the AI access to the dialog history. It’s not a full restore, but the AI will be able to read the context.

23

So, because of the update you made, all those chats I was running in parallel are now useless because there are only two of them in the .cursor folder, and even those .txt files won’t open because they’re too big. As you said, I know the AI ​​won’t understand it at all when I tell it to create and use an .md file. So, thank you, cursor. Really, thank you…

24

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.