Recent update is a noob

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

After the recent update, I am keep facing resume button or try again button saying having trouble connecting the model provider. I think this is related to the context size if I am using the pro. Also, not like before, auto summarization seems to not working well. It keeps halting with thoughts and not working and intended.

Basically, I keep face try again or resume after some conversation and this is very irritating. It didn’t happen before.

Steps to Reproduce

Run agent for some time and context is full

Expected Behavior

when context is full or agent is running with many queued requests, it at some point stop and fail to connect model provider.

Operating System

MacOS
Linux

Version Information

Version: 2.4.22 (Universal)
VSCode Version: 1.105.1
Commit: 618c607a249dd7fd2ffc662c6531143833bebd40
Date: 2026-01-26T22:51:47.692Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

For AI issues: add Request ID with privacy disabled

Request ID: 6ce8a540-b2eb-4d89-8d7e-a4c74fe810cb
{“error”:56,“details”:{“title”:“Network Error”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“isRetryable”:true,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
[resource_exhausted] Error
LTe: [resource_exhausted] Error
at Gmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:38348)
at Hmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:37251)
at rpf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4395)
at fva.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)
at async Hyt.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34196:57047)
at async Zpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34245:7695)
at async Zpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34245:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)
at async Ei (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32994:3808)

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. This is a known issue: the agent can crash when the context is too large.

Similar reports: Persistent Connection Error

Try these workarounds:

  • Start the agent in a new chat tab instead of continuing the old one (this resets the context)
  • Disable any MCP servers you’re not using in Settings > MCP (they add context)
  • If you’re using a custom model, switch to Claude Sonnet or GPT-5 (they’re more stable)
  • Before starting the agent, make sure autosaving large files is turned off

Let me know if any of this helps.