[P0] Cursor not usable for me

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am using cursor cloud and getting this error on older agent chats.
Agent encountered an error
The team is on it. Retry or send a follow-up below.

When i try to load a new chat, it just closes and vanishes.

Steps to Reproduce

Uploaded the video and screenshot.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.20.0
VS Code Extension API: 1.128.0
Commit: 4c0fe9acf024d051c47ffe28c48918ef6835f370
Date: 2026-09-07T23:10:23.198Z
Layout: Agent Window
Build Type: Stable
Release Track: Nightly
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.3.0

For AI issues: which model did you use?

grok 4.6

Does this stop you from using Cursor

Yes - Cursor is unusable

This issue happened when i updated my cursor

Thanks for flagging this, @Arpit_Singh!

A couple of quick questions to help narrow things down:

  1. Can you start local agents?
  2. Can you start agents from cursor.com/agents?
  3. If both are failing, does rolling back to 3.19 (available at Cursor · Download) resolve it?

That last step would help us confirm whether this is really upgrade-related. Let us know what you find!

On browser when using cloud agent i am getting

[ { “code”: “invalid_type”, “expected”: “object”, “received”: “number”, “path”: [ “ports”, 0 ], “message”: “Expected object, received number” } ] Here is the environment.json: jsonc { "install": "bash .cursor/setup_script.sh", "start": "bash .cursor/start_script.sh", "ports": [8765] }

Things are working fine in local cursor. Only issue with cloud agents.

Hey @Arpit_Singh, thanks, that error message pins it down exactly!

The ports field in .cursor/environment.json expects a list of objects, not bare numbers. So this line is what’s stopping cloud agents from starting:

"ports": [8765]

Change it to:

"ports": [{ "name": "app", "port": 8765 }]

(The name is optional and just a label, so [{ "port": 8765 }] also works. If you don’t actually need the port forwarded, you can remove the ports key entirely.)

Commit that to main, then start a new cloud agent or open one of the older chats and press Retry. Both should work again, and the environment builds on the dashboard will go green on their next run.

The rest of your file (install and start) looks fine. Local agents were unaffected because they never read this file.

Sorry the error in Cursor itself was so unhelpful. We’re looking at showing the actual validation message there, the way the web version does.