An unexpected error occurred. Request ID: acd028de-c03d-4211-a013-f248c9265810

Support Bug Reports
1

Where does the bug appear (feature/product)?

  • [x] Editor, Tab & Chat (autocomplete, Composer, in-editor agent)

  • [ ] Terminal & commands

  • [ ] Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)

  • [ ] MCP & tools

  • [ ] Cloud Agents & Automations (cursor.com/agents, scheduled/event)

  • [ ] BugBot & Code Review

  • [ ] Cursor CLI

  • [ ] Cursor Mobile

  • [ ] Remote (SSH / Dev Containers / WSL)

  • [ ] Account, billing & login

  • [ ] Something else…

Describe the Bug Since mid-September 2026, the Cursor agent stopped working and throws an error when invoked. The rest of the editor and IDE environment continue to work normally, but the agent feature fails completely.

Steps to Reproduce

  1. Open Cursor.

  2. Attempt to invoke or run a prompt using the in-editor Agent / Composer feature.

  3. An error occurs and the agent fails to respond.

Expected Behavior The Cursor agent should process prompts and generate responses/code edits without throwing an error.

Screenshots / Screen Recordings (Attach any screenshots or screen recordings of the error message here if available)

Operating System

  • [ ] Windows 10/11

  • [x] MacOS

  • [ ] Linux

Version Information For Cursor IDE:

  • IDE Version: 3.21.16

  • VSCode Version: 1.128.0

  • Commit: 8ae78e8eee1e63479c7e0504b664bc0a80c68000

  • Date: 2026-09-19T06:43:22.276Z

  • OS: Darwin arm64 27.0.0

For AI issues: which model did you use? (Specify model name if applicable, e.g., Claude 3.5 Sonnet, Auto)

For AI issues: add Request ID with privacy disabled Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1

Additional Information Troubleshooting steps already attempted without success:

  • Restarted Cursor and rebooted the system.

  • Completely reinstalled and updated Cursor to the latest version.

  • Toggled and changed Privacy Mode settings.

Does this stop you from using Cursor?

  • [x] Yes - Cursor is unusable

  • [ ] Sometimes - I can sometimes use Cursor

  • [ ] No - Cursor works, but with this issue

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

8

Hey @Mostafa_Moradi,

This is a macOS 27 issue we’re tracking, and there’s a fix that’s worked for others on the same setup: macOS 27 doesn’t keep Rosetta 2 after the upgrade, so an old Intel git the agent relies on can’t run and local steps time out.

  1. Install Rosetta, then fully quit Cursor (Cmd+Q) and reopen:
softwareupdate --install-rosetta --agree-to-license
  1. If it still fails, in Terminal run which -a git and file "$(which git)". If a git in /usr/local/bin shows as x86_64 only, make sure the arm64 one (/usr/bin/git) is first on your PATH, then quit and reopen Cursor.

Step 1 alone fixes it for most people on macOS 27. More context and others confirming here: macOS 27 agent thread. Let me know if that doesn’t do it.

9

Solved! Thanks for your support! :slight_smile: