Support on how to get cursor running

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor agent execution broken after latest update — can’t prototype with Orchard

After the latest Cursor update, agent execution is completely non-functional for me. Here’s what’s happening:

Setup: Orchard prototype. Xcode opens, simulator loads, Swift template appears — all fine. But Cursor doesn’t register anything I type.

Every command times out with an agent execution error.

What I’ve tried:

  • Followed the fix from this forum thread: Agent execution timeout error in Cursor - #3 by deanrie
  • That logged me out and I couldn’t log back in (login wasn’t registering)
  • Cleared cache via terminal, was able to log back in
  • Same issue returned — Cursor is “dead,” times out on every input

Environment: macOS, latest Cursor update, Orchard integration

This has been going on for 2 days. I’ve been going back and forth between the login issue and the timeout issue. Multiple people seem to be hitting this after the latest update. Any help would be appreciated — I just want to prototype with Orchard and haven’t been able to all week.

Steps to Reproduce

Steps to Reproduce:

  1. Open Orchard and click “Open” on a prototype
  2. Xcode launches, simulator opens, Swift template loads — all working
  3. In Cursor, type any prompt or command
  4. Cursor shows a loading/thinking state, then times out with an agent execution error
  5. No commands are processed — Cursor does not register any input

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 2.6.11 (Universal)
VSCode Version: 1.105.1
Commit: 8c95649f251a168cc4bb34c89531fae7db4bd990
Date: 2026-03-03T18:57:48.001Z (2 days ago)
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.1.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey there.

How do your Network Diagnostics look? Any errors? Does switching to HTTP/1.1 change the behavior?

I can see that you’re also in touch with someone via [email protected] – make sure you follow-up with our support colleagues!