Server failing to connect

[V_M]

In a new chat (IDE and Agent Window), a prompt (plan/agent) is answered for the first time but the second prompt in the same chat throws this error:

The server failed 4 times. Please try again, or contact support if the issue persists.

Generates a new request id on every trial: 0ed73456-3481-4b8e-9756-1996979cf124

[invalid_argument] Failed to resolve request context blob
RetriableError: [invalid_argument] Failed to resolve request context blob
at 5 (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9000:131224)
at FOo._executeTurn (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9000:151653)
at async FOo.executeTurn (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9000:140031)
at async gpe.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8995:15873)
at async Fva.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:18768:23720)
at async Fva.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:18768:48269)
at async SEe._submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8968:5134)
at async SEe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8963:77381)

**This is stopping the work completely. You can’t continue the same chat thread. This is leading to higher costs and very poor experience.
**

Checked on Cursor versions: 3.25 and 3.26 and 3.27.
System & OS: Apple M4 Pro, macOS: Golden Gate 27.0.1
Network: No Proxy, No VPN
Checked with HTTP1.1 and HTTP2. The Run diagnostics throws issues intermittently. My colleague using the same internet connection sitting next to me is not facing any issues. PS: Attached screenshots.

I’ve recently moved from individual account to team account and merged personal account with a team account email/seat.

[system]

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

• Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
• Terminal & commands
• Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
• MCP & tools
• Cloud Agents & Automations (cursor.com/agents, scheduled/event)
• BugBot & Code Review
• Cursor CLI
• Cursor Mobile
• Remote (SSH / Dev Containers / WSL)
• Account, billing & login
• Something else…

---

Describe the Bug
A clear and concise description of what the bug is.

---

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

1. …
2. …
3. …

---

Expected Behavior
What is meant to happen here that isn’t working correctly?

---

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

---

Operating System

• Windows 10/11
• MacOS
• Linux

---

Version Information

• For Cursor IDE: Menu → About Cursor → Copy
• For Cursor CLI: Run agent about in your terminal

IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

---

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

---

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

---

Additional Information
Add any other context about the problem here.

---

Does this stop you from using Cursor?

• Yes - Cursor is unusable
• Sometimes - I can sometimes use Cursor
• No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

[V_M]

This appears to be a bug, but cannot say for sure. The required details are already added in the main ticket: Server failing to connect

[Colin]

Hey @V_M,

Thanks for the detailed report and the request ID, that made this much easier to track down.

This comes from how your privacy settings line up after the move to the team account. Your own account is set to the strictest privacy level, while the team you’re working in enforces a different one. When those two disagree, Cursor sends follow-up messages in a chat in a form our servers then refuse. That’s why the first message in a new chat works and every message after it fails, and why your colleague on the same network doesn’t see it. It isn’t your network, so you can leave the HTTP and proxy settings as they were.

I’ve flagged this to the team so the two settings can’t get out of step like this.

You should be able to fix this yourself, without changing anything on the team. Your own account is still set to Privacy Mode (Legacy), and switching it to match the team should stop follow-up messages failing.

1. Open the Cursor dashboard at cursor.com/dashboard and open your personal Settings.
2. Go to Privacy.
3. Next to your personal privacy mode, click Switch my account (or Edit) and choose Privacy Mode (no training).
4. Restart Cursor and start a new chat.

This only changes your personal setting, and it matches the Privacy Mode your team already enforces. Once you move off Legacy you won’t be able to switch back to it.

Chats you started before the change may still fail on follow-ups, so use new ones. If a follow-up in a new chat still fails after this, let me know.

[V_M]

Hi Colin, thanks for the reply and sharing the bug fix. Cursor is working fine now. The ticket can be closed.