Cursor agent won't start on Windows: why it says "agent process didn't respond" and how to fix it

Last verified: November 21, 2026
Since late October, people using Cursor on Windows have been opening a chat, sending a prompt and getting an error before the agent writes a single line: the agent "couldn't start because Cursor's agent process didn't respond." The message appears on every request, with every model, and retrying or restarting the app does not help. Because the text of the error suggests checking antivirus software and HTTPS proxies, it is easy to lose time on firewall rules and network settings that, according to Cursor staff, have nothing to do with this problem.
Cursor staff have described it on the official forum as a known Windows issue in versions 3.28 and 3.29, in which the local agent process never starts, and they have said it is not caused by the network or by antivirus software. The quickest fix is to open the Agent chat in the editor window with Ctrl+Shift+N, or to go back to Cursor 3.27 and switch updates to manual. The problem affects the Windows desktop app; the reports collected so far come from Windows 10 and 11 machines on both the default and the Nightly release tracks, starting with version 3.28 at the end of October 2026.
··········
THE CURSOR "AGENT PROCESS DIDN'T RESPOND" ERROR AND WHERE IT APPEARS.
The error shows up inside the chat panel, in place of the agent's answer, as soon as a request is sent. The full text quoted in the bug reports on the Cursor forum reads as follows.
An unexpected error occurred.
The agent couldn't start because Cursor's agent process didn't respond.
Retry, or reconnect if you're using a remote host.
If it keeps failing locally and antivirus or a proxy inspects HTTPS traffic, run Network Diagnostics in Cursor Settings.Underneath, the details of the request show the same sentence prefixed by `AgentTurnClassifiedError:` and a request ID in the usual UUID format. One report also contains a stack trace that mentions waiting for the "agent host bridge", the internal link between the Cursor window and the background process that runs the agent. That background process is what fails to start, which explains why the error is identical whatever model is selected and whatever project is open.
The pointer to Network Diagnostics is new in version 3.28. Cursor's own release notes for that version say that agent startup failures "now point to Network Diagnostics in Cursor Settings". The change only rewords the error and gives users a place to look; it does not mean the network is the cause in every case.
··········
CURSOR VERSIONS AFFECTED BY THE WINDOWS AGENT START FAILURE.
The table below combines the official download page and release notes with the staff answers on the forum, as checked on November 21, 2026.
........
Cursor version | Status for this error | Source |
3.27 | Works; staff recommend it as the fallback | Cursor staff on the forum |
3.28 | Affected on Windows, Agents Window | Cursor staff on the forum, user reports |
3.29 | Affected on Windows | Cursor staff on the forum, user report on 3.29.9 |
3.30 | Release notes list agent reliability fixes, none for this error | Cursor release notes |
3.31 | Latest on the download page, notes not yet published | Cursor download page |
........
The 3.30 notes mention that cancelling an agent request now ends it immediately and that waking from sleep no longer triggers false extension host warnings, but nothing about the agent process failing to start. No staff post or changelog entry found during this check says the problem is fixed, so anyone on 3.30 or 3.31 who still sees the message should use the workarounds below.
··········
WHY CURSOR'S AGENT FAILS TO START ON WINDOWS: CAUSES, CHECKS AND FIXES.
Most people hitting the error since late October are dealing with the first cause in the table. The others explain why the problem can return after a fix, or why the same message can appear for a different reason on managed computers.
........
Cause | How to check | Fix |
Known Windows bug in Cursor 3.28 and 3.29 | Your Cursor version number starts with 3.28 or 3.29 | Use the editor window chat, or install 3.27 |
You are using the Agents Window layout | The error appears in the Agents Window layout | Press Ctrl+Shift+N or choose File > Open IDE and chat there |
Cursor updated itself back to 3.28 or 3.29 | The error returns after a restart; the version changed again | Set update.mode to manual before restarting |
You are on the Nightly release track | Cursor Settings > Beta > Update Access is not set to Default | Set Update Access to Default, then install 3.27 |
Your company manages Cursor updates | The update.mode setting is locked or ignored | Ask the administrator, who controls the UpdateMode policy |
HTTPS inspection or endpoint security (other cases) | Network Diagnostics in Cursor Settings reports a failure | Follow Cursor's network and endpoint security guidance |
........
··········
HOW TO FIX THE CURSOR AGENT START ERROR, STEP BY STEP.
The first fix keeps the current version and takes a few seconds. A Cursor staff member wrote on November 2 that the problem concerns the Agents Window in 3.28 on Windows and that the Agent chat in the classic editor window "isn't affected".
1. In Cursor, press Ctrl+Shift+N, or open the File menu and choose Open IDE.
2. In the editor window that opens, use the Agent chat panel instead of the Agents Window.
3. Send a short prompt to confirm that the agent answers.
If the editor window is not an option, the second fix is to install the last version that works. Another staff member confirmed on November 9 that installing 3.27 "gets the agent working again". Cursor's download page still offers Windows installers for 3.27, alongside the newer builds, in both user and system variants for x64 and ARM64. Cursor's help pages say that a new installer can be run over the existing installation and that settings and chat history carry over.
1. If you use Nightly builds, open Cursor Settings, go to Beta and set Update Access to Default first. Staff warned that Nightly would otherwise update you "straight back to 3.28".
2. Download the Windows installer for 3.27 from the official Cursor download page and run it.
3. Before Cursor can update itself again, press Ctrl+Shift+P and run "Preferences: Open User Settings (JSON)".
4. Add the line below inside the settings object, save the file and restart Cursor.
"update.mode": "manual"Cursor documents `update.mode` in its help center: with `manual`, Cursor only updates when you check for updates yourself, and with `none` updates are off entirely. The same setting can also be found through "Preferences: Open Settings (UI)" by searching for update.mode. When a newer version lists a fix for the problem, you can check for updates by hand and return to the current release.
Version 3.27 will not stay available forever. Cursor's help pages explain that the download page carries the latest release and a few recent ones, and that versions which have aged out are no longer offered. Cursor's help center also has a troubleshooting page on the minimum version the service supports, another reason to treat the downgrade as temporary.
··········
CURSOR ON MANAGED WINDOWS PCS: UPDATE POLICIES, ANTIVIRUS AND NETWORK CHECKS.
On a work computer the downgrade may not stick. Staff noted that a centrally managed setup can lock the update setting, and Cursor's enterprise documentation describes an UpdateMode policy, delivered through device management, that overrides what the user sets. In that case the editor window workaround is the practical option until the IT team approves a different version.
The error text points to antivirus and HTTPS inspection because those genuinely can break Cursor in other situations. For the known 3.28 and 3.29 issue, staff said twice that the network and antivirus software are not the cause. Running the built-in check still costs little and rules out a second problem.
1. Open Cursor Settings and run Network Diagnostics.
2. If it reports failures, follow Cursor's network troubleshooting page and our guide to Cursor's "Connection failed" error and its network causes.
3. On managed machines, Cursor's agent troubleshooting page lists endpoint security software (antivirus and EDR) as one possible cause of agent start problems, and the company publishes separate guidance for endpoint security teams.
··········
WHAT CURSOR HAS CONFIRMED ABOUT THE ERROR AND WHAT COMES ONLY FROM USERS.
The table separates statements by Cursor staff and official pages from what has only been reported by individual users.
........
Statement | Status |
Known Windows issue in 3.28 and 3.29; the local agent process never starts | Cursor staff, forum, November 2 and 9 |
Not caused by network or antivirus | Cursor staff, forum |
Agent chat in the editor window is not affected | Cursor staff, forum, November 2 |
Version 3.27 works; update.mode manual prevents the return to 3.29 | Cursor staff, forum, November 9 |
update.mode values and the UpdateMode admin policy | Cursor help center and enterprise docs |
A fixed version exists | Not stated in any release note or staff post as of November 21 |
Retrying, reconnecting and restarting Cursor does not help | User report on 3.29.9 |
The problem lasts for days and blocks every model | User reports on 3.28.5 and 3.29.9 |
........
Cursor staff also asked affected users for diagnostic data. If you want to help the team, press Ctrl+Shift+P, run "Capture and send debugging Data" and include logs, feature flags and process diagnostics. Cursor's agent troubleshooting page describes a manual alternative for agent start problems: run "Developer: Export Logs...", select Main, Window and Extension Host, check the Extension Host entry in the Output panel, and send the zip with your operating system and Cursor version to support. An empty Extension Host panel is, in Cursor's words, a strong diagnostic signal.
··········
AVOIDING THE CURSOR AGENT START FAILURE AFTER FUTURE UPDATES.
The safest routine while the bug is open is to leave updates on manual and read the release notes before each upgrade. Look for an entry about the agent process or agent startup on Windows; the 3.30 notes did not contain one. After installing a new version, open a chat in the Agents Window with a one-line prompt. If the error comes back, the editor window chat still gives you a working agent, and the installer for the previous version remains on the download page for a while.
If the agent starts again but ignores your project instructions, that is a separate problem covered in our guide to Cursor rules that are not applied. For plan limits and how Cursor compares with other coding agents on price, see our overview of AI coding agent pricing.
··········
CURSOR "AGENT PROCESS DIDN'T RESPOND" ON WINDOWS: CONCLUSIONS.
The message is a Cursor bug on Windows, acknowledged by the company's staff, that appeared with version 3.28 and was still reported on 3.29.9. It stops the background agent process from starting, so the error is the same for every model and project, and retrying, restarting Cursor or changing network and antivirus settings does not change the result.
Two fixes have staff backing: use the Agent chat in the editor window through Ctrl+Shift+N, or install 3.27 and set update.mode to manual so Cursor does not upgrade itself again. Nightly users must switch Update Access to Default first, and managed computers may need the administrator's help. As of November 21, 2026, neither the 3.30 release notes nor any staff post names a version that fixes the problem, and the notes for 3.31 had not yet been published.
··········
FOLLOW US FOR MORE.
·····
DATA STUDIOS
·····
datastudios.org




