Error launching cloud agent

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When I try and run a Cloud Agent from the IDE I get the following error:

Request ID: 78fee2a0-bd07-4728-8391-bdf8341cd3a2
ConnectError: [internal] internal error
at t (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:43784:42407)
at async Object.startBackgroundComposerFromSnapshot (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34083:4386)
at async Hid.startSingleBackgroundComposer (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49775:16539)
at async Promise.all (index 0)
at async Hid.startNewBackgroundComposer (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49775:9930)
at async g (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46817:21149)
at async p (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46817:19108)
at async Proxy.callback (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46817:27808)

Steps to Reproduce

Change the agent drop-down to Cloud then try and run an agent with any prompt

Request ID: 151cb273-319e-4345-bf29-068532ea16da
ConnectError: [internal] internal error
at t (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:43784:42407)
at async Object.startBackgroundComposerFromSnapshot (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34083:4386)
at async Hid.startSingleBackgroundComposer (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49775:16539)
at async Promise.all (index 0)
at async Hid.startNewBackgroundComposer (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49775:9930)
at async g (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46817:21149)
at async p (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46817:19108)
at async Proxy.callback (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46817:27808)

Our corporate setup installs and upgrades Cursor via Workbrew.

I can use Cloud Agents fine if I navigate to https://cursor.com/agents and runf rom there.

Expected Behavior

I expect the cloud agent to run.

Screenshots / Screen Recordings

Screenshot 2026-03-05 at 3.48.00 PM.png
Screenshot 2026-03-05 at 3.48.00 PM.png745×234 18.9 KB

Operating System

MacOS

Version Information

Version: 2.6.11
VSCode Version: 1.105.1
Commit: 8c95649f251a168cc4bb34c89531fae7db4bd990
Date: 2026-03-03T18:57:48.001Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

For AI issues: which model did you use?

Auto

For AI issues: add Request ID with privacy disabled

Request ID: 151cb273-319e-4345-bf29-068532ea16da

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the report.

Since Cloud Agents work fine via cursor.com/agents but not from the IDE, this points to a network-level issue between the IDE client and our servers, likely related to your corporate environment (Workbrew).

A couple things to try:

  1. Run network diagnostics: Cursor Settings > Network > Run Diagnostics, then share the results here.
  2. Disable HTTP/2: App Settings CMD + , > search for “HTTP/2” > enable “Disable HTTP/2”, then restart Cursor and try again.
  3. If your network uses a proxy or custom certificates, double-check that Cursor is picking them up correctly.

Let me know how it goes. If none of this helps, I can escalate with your request IDs so we can take a closer look on the server side.

4

Diagnostic results below - all ok. I had to remove the links from the diagnostic output to make this post successful.

Disabling HTTP/2 prevented the agent from starting. No error was reported; I gave up after 5 minutes.

However, after I re-enabled HTTP/2 and started a new cloud agent, it began working properly. My cloud agent was kicked off and started working.

Cursor Network Diagnostic Results

DNS: Success
Logs:
[2026-03-05T13:24:40.658Z] Host: api2.cursor.sh
[2026-03-05T13:24:40.659Z] Servers: fe80::1,192.168.18.48,1.1.1.1
[2026-03-05T13:24:40.659Z] Resolved to 54.164.221.176 in 8ms
[2026-03-05T13:24:40.728Z] Resolved to 54.164.221.176 in 57ms
[2026-03-05T13:24:40.739Z] Resolved to 54.164.221.176 in 5ms
[2026-03-05T13:24:40.743Z] Resolved to 54.164.221.176 in 3ms
[2026-03-05T13:24:40.748Z] Host: api2.cursor.sh
[2026-03-05T13:24:40.748Z] Servers: system
[2026-03-05T13:24:40.748Z] Resolved to 54.164.221.176, 52.86.248.14, 34.231.189.8, 52.0.113.97, 18.235.186.193, 54.160.14.42, 3.208.169.199, 18.211.220.239 in 5ms
[2026-03-05T13:24:40.750Z] Resolved to 54.164.221.176, 52.86.248.14, 34.231.189.8, 52.0.113.97, 18.235.186.193, 54.160.14.42, 3.208.169.199, 18.211.220.239 in 0ms
[2026-03-05T13:24:40.750Z] Resolved to 54.164.221.176, 52.86.248.14, 34.231.189.8, 52.0.113.97, 18.235.186.193, 54.160.14.42, 3.208.169.199, 18.211.220.239 in 0ms
[2026-03-05T13:24:40.750Z] Resolved to 54.164.221.176, 52.86.248.14, 34.231.189.8, 52.0.113.97, 18.235.186.193, 54.160.14.42, 3.208.169.199, 18.211.220.239 in 0ms
[2026-03-05T13:24:40.750Z] Result: true

HTTP/2: Success
Logs:
[2026-03-05T13:24:40.634Z] Start
[2026-03-05T13:24:41.114Z] Host: api2.cursor.sh
[2026-03-05T13:24:41.114Z] Protocol: h2
[2026-03-05T13:24:41.114Z] Result: true in 480ms

SSL: Success
Logs:
[2026-03-05T13:24:40.634Z] Start
[2026-03-05T13:24:41.347Z] URL:
[2026-03-05T13:24:41.347Z] Status: 200
[2026-03-05T13:24:41.347Z] IP: 54.164.221.176
[2026-03-05T13:24:41.347Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
[2026-03-05T13:24:41.347Z] Name: api2.cursor.sh
[2026-03-05T13:24:41.347Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2026-03-05T13:24:41.347Z] DNS Time: 5ms
[2026-03-05T13:24:41.347Z] Connect Time: 235ms
[2026-03-05T13:24:41.347Z] TLS Time: 233ms
[2026-03-05T13:24:41.347Z] Result: true in 713ms

API: Success
Logs:
[2026-03-05T13:24:40.635Z] Start
[2026-03-05T13:24:40.820Z] Result: true

Ping: Success
Logs:
[2026-03-05T13:24:40.636Z] Sending ping 1
[2026-03-05T13:24:40.768Z] Response: ‘ping’ in 132ms
[2026-03-05T13:24:40.768Z] Sending ping 2
[2026-03-05T13:24:40.820Z] Response: ‘ping’ in 52ms
[2026-03-05T13:24:40.820Z] Sending ping 3
[2026-03-05T13:24:40.836Z] Response: ‘ping’ in 16ms
[2026-03-05T13:24:40.836Z] Sending ping 4
[2026-03-05T13:24:40.853Z] Response: ‘ping’ in 17ms
[2026-03-05T13:24:40.853Z] Sending ping 5
[2026-03-05T13:24:40.869Z] Response: ‘ping’ in 16ms
[2026-03-05T13:24:40.869Z] Result: true

Chat: Success
Logs:
[2026-03-05T13:24:40.636Z] Starting stream
[2026-03-05T13:24:40.770Z] Response: ‘foo’ in 132ms
[2026-03-05T13:24:41.770Z] Response: ‘foo’ in 1000ms
[2026-03-05T13:24:42.770Z] Response: ‘foo’ in 1000ms
[2026-03-05T13:24:43.773Z] Response: ‘foo’ in 1003ms
[2026-03-05T13:24:44.772Z] Response: ‘foo’ in 999ms
[2026-03-05T13:24:45.772Z] Result: true

Agent: Success
Logs:
[2026-03-05T13:24:40.638Z] Starting stream
[2026-03-05T13:24:40.638Z] Pushing first message
[2026-03-05T13:24:40.708Z] Response: ‘foo’ in 70ms
[2026-03-05T13:24:41.209Z] Pushing next message
[2026-03-05T13:24:41.219Z] Response: ‘foo’ in 511ms
[2026-03-05T13:24:41.720Z] Pushing next message
[2026-03-05T13:24:41.729Z] Response: ‘foo’ in 510ms
[2026-03-05T13:24:42.230Z] Pushing next message
[2026-03-05T13:24:42.241Z] Response: ‘foo’ in 512ms
[2026-03-05T13:24:42.742Z] Pushing next message
[2026-03-05T13:24:42.751Z] Response: ‘foo’ in 510ms
[2026-03-05T13:24:42.751Z] Result: true

Marketplace: Success
Logs:
[2026-03-05T13:24:40.622Z] Host: marketplace.cursorapi.com
[2026-03-05T13:24:40.869Z] Response in 247ms
[2026-03-05T13:24:40.869Z] Response: 200
[2026-03-05T13:24:40.869Z] Response Type: cors
[2026-03-05T13:24:40.869Z] Server: null
[2026-03-05T13:24:40.869Z] Result: OK in 247ms

Authentication: Success
Logs:
[2026-03-05T13:24:40.626Z] Host: prod.authentication.cursor.sh
[2026-03-05T13:24:41.414Z] Response: 200 in 788ms

Authentication UI: Success
Logs:
[2026-03-05T13:24:40.634Z] DNS lookup: authenticator.cursor.sh
[2026-03-05T13:24:40.676Z] Resolved authenticator.cursor.sh to 172.64.152.23 in 32ms

Cursor Tab: Success
Logs:
[2026-03-05T13:24:40.634Z] DNS lookup: api3.cursor.sh
[2026-03-05T13:24:40.663Z] Resolved api3.cursor.sh to 104.18.19.125 in 20ms

Agent Endpoint: Success
Logs:
[2026-03-05T13:24:40.634Z] DNS lookup: agent.api5.cursor.sh
[2026-03-05T13:24:40.721Z] Resolved agent.api5.cursor.sh to 50.18.248.73 in 74ms

Codebase Indexing: Success
Logs:
[2026-03-05T13:24:40.634Z] DNS lookup: repo42.cursor.sh
[2026-03-05T13:24:40.709Z] Resolved repo42.cursor.sh to 100.51.113.220 in 67ms

Downloads: Success
Logs:
[2026-03-05T13:24:40.630Z] Host:
[2026-03-05T13:24:41.576Z] Response: 403 in 946ms

CDN: Success
Logs:
[2026-03-05T13:24:40.633Z] Host:
[2026-03-05T13:24:41.034Z] Response: 404 in 401ms

5

Glad to hear that switching fixed it and everything is working again. The diagnostics look clean, so it was most likely a short server-side issue, not something on your end.

If it happens again, try this in order:

  1. Restart Cursor, then try starting the cloud agent again.
  2. If the error still happens, grab a new Request ID and share it here.

Let me know if it comes back and we can dig in further.

6

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.