Agent keep reconnecting when started to build plan

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I click “Build” button inside plan with opus 4.7, it keep “Reconnecting” and “Planning next move” then stop excecuting

Steps to Reproduce

  1. Open cursor IDE
  2. Make a plan using “Plan” option
    3, Build plan using Opus 4.7 (I have used Composer 2.5 and it still works as normal)

Expected Behavior

Agent can build plan as normal

Screenshots / Screen Recordings

Screenshot 2026-05-22 114535.png
Screenshot 2026-05-22 114535.png445×116 3.52 KB

Operating System

Windows 10/11

Version Information

Version: 3.5.17 (user setup)
VSCode Version: 1.105.1
Commit: d5b2fc092e16007956c9e5047f76097b9e626ca0
Date: 2026-05-20T02:43:31.559Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.22000

For AI issues: which model did you use?

Opus 4.7

For AI issues: add Request ID with privacy disabled

RequestID: 0d1536d2-b622-4447-aecc-eb674daae62a

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

6

Thanks for the detailed report and the request ID. The fact that Composer 2.5 works fine but Opus 4.7 doesn’t is a helpful data point.

A few things that would help us narrow this down:

  1. Run Network Diagnostics: Cursor Settings > Network > Run Diagnostics, then share the results here as a screenshot

  2. Disable HTTP/2: Open Settings (Ctrl+,), search for “HTTP/2”, turn on Disable HTTP/2, then fully quit and restart Cursor (not just Reload Window). Test Plan Build with Opus 4.7 again and let us know if it helps

  3. New Request ID: After trying the steps above, if the issue still happens, copy the Request ID from the failing request (three-dot menu in chat > Copy Request ID) and share it here. The original ID you shared (0d1536d2-b622-4447-aecc-eb674daae62a) didn’t surface in our logs, so a fresh one from a failed Build attempt would be very helpful

You can also find related reports in this thread where other users found some of these workarounds helpful.