Unexpected error on new install

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Repeatedly get the error (with various IDs):
An unexpected error occurred. Request ID: c14fba27-d59c-47de-b6fe-8b4c49cc5738

Steps to Reproduce

I open Cursor on a clean install on a new machine, select the local machine and repository and send a message. Either auto mode or Grok. Pressing try again doesn’t fix it. The first time I tried I accidentally tried to use a cloud agent, which tried for a while and failed, perhaps that broke it.

It is working fine on another Mac.

Expected Behavior

I should be able to use cursor.

Operating System

MacOS

Version Information

version:%203.12.30%20(Universal)%0AVS%20Code%20Extension%20API%3A%201.128.0%0ACommit%3A%0A63a2996a10d9e476b6c28e951d-%0Ad7691d9c0cf480%0ADate%3A%202026-07-21T22%3A50%3A03.568Z%20(1%0Aday%20ago)%0ALayout%3A%20Agent%20Window%0ABuild%20Type%3A%20Stable%0ARelease%20Track%3A%20Default%0AElectron%3A%2040.10.3%0AChromium%3A%20144.0.7559.236%0ANode.js%3A%2024.15.0%0AV8%3A%2014.4.258.32-electron.0%0Axterm.js%3A%206.1.0-beta.256%0AOS%3A%20Darwin%20arm64%2024.3.0

For AI issues: which model did you use?

Auto, Grok

Does this stop you from using Cursor

Yes - Cursor is unusable

6

Hi @EdLyons Thank you for the forum post! I took a look at this and I see that the error is happening locally on the new machine before the request leaves it, which is why the Request IDs don’t show up on our side and why Try again keeps failing.

What’s happening: in the Agents Window, an agent is tied to the project it was started in. That project isn’t set up on the new Mac yet, so the agent can’t bind to it, and the send fails instantly. Try again just reuses the stuck chat.

To get unblocked:

  1. Clone/open the project folder locally on the new Mac first, so Cursor has the real workspace.
  2. Start a brand new agent chat from that open project. Don’t reuse the errored chats or Try again, since both reuse the stuck session.
  3. If a window still looks wedged, run Developer: Reload Window (Cmd+Shift+P) and start fresh.

The cloud agent you tried failed separately: it looked for a self-hosted worker (your other Mac) and found none eligible from the new machine, so it stopped at startup. Nothing was corrupted. For cloud runs, pick the Cloud option explicitly instead of the self-hosted worker.

Give that a try and let me know how it goes! If a fresh chat from the opened project still errors, reply with the new Request ID and I’ll dig in.

7

Hi @kevinn, thanks for your message - that fixed it. Would be a good idea to improve the UX there a bit!