Cannot use local agents

Support Bug Reports
, ,
1

I’m on version 3.16.17 (Universal) on a 2026 MacBook Air M5 with 24GB memory.

Where does the bug appear (feature/product)?

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

Describe the Bug
Hi, I am trying to continue a session I was working on last night, and this morning I updated to MacOS 27 Public Beta, and cursor no longer works for any existing or new local conversations.

After about a minute, it shows this error:
The agent execution provider did not respond in time. This may indicate the extension host is not running or is unresponsive. Request ID: daa05183-313e-410c-87cc-7a9ebf39df92

I have tried fully reinstalling the app, starting cursor without extensions, deleting the workspaceStorage folder, changing HTTP compatibility mode, enabling Legacy Terminal Tool, running network diagnostics, killing cursor processes, restarting my computer, etc. and nothing is working.

Steps to Reproduce
No idea, possibly just upgrade to MacOS 27?

Expected Behavior
Local chats should work and the agent should respond

Screenshots / Screen Recordings
N/A

Operating System

  • MacOS 27 Public Beta

Version Information

Version: 3.16.17 (Universal)
VS Code Extension API: 1.128.0
Commit: 6b2afae0257df2bb5e1835f15165dc2f0de056b0
Date: 2026-08-14T01:41:12.803Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 27.0.0

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

For AI issues: add Request ID with privacy disabled
daa05183-313e-410c-87cc-7a9ebf39df92 (privacy was enabled)

1f7f6177-fea6-42ce-92a3-03a67225a56f (privacy was disabled)

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
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!

5

I also cannot switch a local conversation to the cloud
spawn Unknown system error -86 Request ID: bc-d1a612ef-5fde-459f-a498-a6eba3136f1c

6

I updated to the new MacOS 27 Public Beta and after restart, it works again. I suspect it was the restart combined with one of the debugging steps I took, not necessarily a version of the public beta that broke this but I could be wrong…very unfortunate because I could not use this for a whole day of work :frowning: