Agent stuck at "planning next steps" - No first token received within 6s (Win x64)

Describe the Bug

Hi,

I’m experiencing an issue where the Agent consistently gets stuck at “planning next steps” and times out with the following error in the logs:

[composer] No first token received within 6s

Environment:

OS: Windows x64
Channel: Stable
Client version: 2.4.37
What I’ve tried:

Enabled HTTP/1.1 compatibility mode in Network settings
Tested with and without VPN - same result
Tested across all available models - all affected
Steps to reproduce:

Open any chat or Agent conversation
Enter any prompt
Agent hangs at “planning next steps” and never responds
Expected behavior: Agent begins responding within a few seconds.

Request ID: ded3ea33-35d4-4acc-b2db-909a89642e8c

Any help would be appreciated. Happy to provide Developer Tools console output or diagnostics results if needed.

Steps to Reproduce

Steps to reproduce:

Open any chat or Agent conversation
Enter any prompt
Agent hangs at “planning next steps” and never responds
Expected behavior: Agent begins responding within a few seconds.

Operating System

Windows 10/11

Version Information

Version: 2.4.37 (system setup)
VSCode Version: 1.105.1
Commit: 7b9c34466f5c119e93c3e654bb80fe9306b6cc70
Date: 2026-02-12T23:15:35.107Z
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: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, a couple of things stand out here.

First, you’re on version 2.4.37, which is pretty old (from February 12). Since then, there have been a few fixes related to streaming and agent timeouts. Please update to the latest stable version: Help > Check for Updates, restart Cursor, and try again.

If the issue still happens after updating:

  1. Run network diagnostics: Cursor Settings > Network > Run Diagnostics and share a screenshot of the results here.
  2. Try in a clean, empty folder (a new project with a single file) to rule out project-specific issues.

The team is aware of freezes at the “Planning next moves” step, your report and request ID help with tracking. But the version mismatch alone could explain it, so let’s start with the update.

Let me know how it goes after updating.


My cursor is also stuck with same error reported by OP, here is the network diagnostics result. Cursor version is 2.6.18.

I am enterprise premium on Windows.