Unable to connect to Backgroup Agent Setup

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Hello,

When trying to setup the background agent on interactive mode, I’m alway shown the following error:

Failed to connect to the remote extension host server (Error: [invalid_argument] Error)

Due to this, I’ve been unable to set up the Cursor background agent.

I’ve already checked my network connection by running the network diagnostics, and I’ve also ensured that there’s no VPN or Proxy setup on my machine.

Attached you’ll find a screenshot of the issue, and the error logs from the developer tools.

workbench.desktop.main.js:2604 Failed to fetch team admin settings: ConnectError: [invalid_argument] Error
    at t (workbench.desktop.main.js:7337:376081)
    at async Object.getTeamAdminSettings (workbench.desktop.main.js:590:254091)
    at async kUu (workbench.desktop.main.js:2604:21898)
    at async xUu (workbench.desktop.main.js:2604:22050)
kUu @ workbench.desktop.main.js:2604
await in kUu
xUu @ workbench.desktop.main.js:2604
r @ workbench.desktop.main.js:2604
workbench.desktop.main.js:9474 Failed to attach logs: ConnectError: [canceled] This operation was aborted
    at t7l.$endAiConnectTransportReportError (workbench.desktop.main.js:7337:375292)
    at TMr._doInvokeHandler (workbench.desktop.main.js:489:35946)
    at TMr._invokeHandler (workbench.desktop.main.js:489:35688)
    at TMr._receiveRequest (workbench.desktop.main.js:489:34453)
    at TMr._receiveOneMessage (workbench.desktop.main.js:489:33275)
    at cEt.value (workbench.desktop.main.js:489:31369)
    at _e._deliver (workbench.desktop.main.js:49:2962)
    at _e.fire (workbench.desktop.main.js:49:3283)
    at cdt.fire (workbench.desktop.main.js:7322:12154)
    at MessagePort.<anonymous> (workbench.desktop.main.js:9402:18292)
I @ workbench.desktop.main.js:9474
await in I
D @ workbench.desktop.main.js:9474
await in D
onTerminalReady @ workbench.desktop.main.js:9474
(anonymous) @ workbench.desktop.main.js:6783
S8o @ workbench.desktop.main.js:276
cet @ workbench.desktop.main.js:276
hDt @ workbench.desktop.main.js:276
lRu @ workbench.desktop.main.js:276
(anonymous) @ workbench.desktop.main.js:276
uG @ workbench.desktop.main.js:276
oRu @ workbench.desktop.main.js:276
uG @ workbench.desktop.main.js:276
w8o @ workbench.desktop.main.js:276
n @ workbench.desktop.main.js:276
(anonymous) @ workbench.desktop.main.js:6783
setTimeout
e.setTimeout @ workbench.desktop.main.js:7347
(anonymous) @ workbench.desktop.main.js:6783
Ll @ workbench.desktop.main.js:276
(anonymous) @ workbench.desktop.main.js:276
S8o @ workbench.desktop.main.js:276
cet @ workbench.desktop.main.js:276
hDt @ workbench.desktop.main.js:276
lRu @ workbench.desktop.main.js:276
(anonymous) @ workbench.desktop.main.js:276
uG @ workbench.desktop.main.js:276
oRu @ workbench.desktop.main.js:276
uG @ workbench.desktop.main.js:276
lP @ workbench.desktop.main.js:276
r @ workbench.desktop.main.js:276
showBackgroundComposerSetupModal @ workbench.desktop.main.js:9420
run @ workbench.desktop.main.js:7202
await in run
handler @ workbench.desktop.main.js:54
invokeFunction @ workbench.desktop.main.js:8194
(anonymous) @ workbench.desktop.main.js:7880
rvs @ workbench.desktop.main.js:52
E5 @ workbench.desktop.main.js:52
_tryExecuteCommand @ workbench.desktop.main.js:7880
executeCommand @ workbench.desktop.main.js:7880
s @ workbench.desktop.main.js:3511
(anonymous) @ workbench.desktop.main.js:3510
workbench.desktop.main.js:55   ERR Cannot register two commands with the same id: _workbench.openUserSettingsEditor: Error: Cannot register two commands with the same id: _workbench.openUserSettingsEditor
    at qe (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:54:18225)
    at t (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8173:101005)
    at cEt.value (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8173:101359)
    at _e._deliver (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
    at _e._deliverQueue (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:3053)
    at _e.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:3390)
    at Rwh.updateCurrentProfile (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9359:127141)
    at bur.changeCurrentProfile (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7896:100796)
    at cEt.value (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7896:97553)
    at _e._deliver (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
    at _e._deliverQueue (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:3053)
    at _e.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:3390)
    at cEt.value (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7896:101959)
    at _e._deliver (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
    at _e.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:3283)
    at u (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7322:897)
    at F6l.onResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7322:1834)
    at F6l.onBuffer (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7322:1682)
    at cEt.value (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7321:1759)
    at _e._deliver (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
    at _e._deliverQueue (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:3053)
    at _e.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:3390)
    at ve (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47:9731) Error: Cannot register two commands with the same id: _workbench.openUserSettingsEditor
    at qe (workbench.desktop.main.js:54:18225)
    at t (workbench.desktop.main.js:8173:101005)
    at cEt.value (workbench.desktop.main.js:8173:101359)
    at _e._deliver (workbench.desktop.main.js:49:2962)
    at _e._deliverQueue (workbench.desktop.main.js:49:3053)
    at _e.fire (workbench.desktop.main.js:49:3390)
    at Rwh.updateCurrentProfile (workbench.desktop.main.js:9359:127141)
    at bur.changeCurrentProfile (workbench.desktop.main.js:7896:100796)
    at cEt.value (workbench.desktop.main.js:7896:97553)
    at _e._deliver (workbench.desktop.main.js:49:2962)
    at _e._deliverQueue (workbench.desktop.main.js:49:3053)
    at _e.fire (workbench.desktop.main.js:49:3390)
    at cEt.value (workbench.desktop.main.js:7896:101959)
    at _e._deliver (workbench.desktop.main.js:49:2962)
    at _e.fire (workbench.desktop.main.js:49:3283)
    at u (workbench.desktop.main.js:7322:897)
    at F6l.onResponse (workbench.desktop.main.js:7322:1834)
    at F6l.onBuffer (workbench.desktop.main.js:7322:1682)
    at cEt.value (workbench.desktop.main.js:7321:1759)
    at _e._deliver (workbench.desktop.main.js:49:2962)
    at _e._deliverQueue (workbench.desktop.main.js:49:3053)
    at _e.fire (workbench.desktop.main.js:49:3390)
    at ve (workbench.desktop.main.js:47:9731)

Can anyone help me with this?

Thank you.

Regards,
Carlos Bernal

Steps to Reproduce

Try to set up the Cursor Background Agent

Cursor > Cursor Settings > Base Environment > Setup Machine Interactively

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.54
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2 Likes

I’ve been experiencing this same thing for a little over a day:

  1. Hit “Re-configure Manual Snapshot” in the cursor settings
  2. Hit “Rebuild Environment” in the snapshot setup UI
  3. Wait for a minute or two
  4. The mini-IDE interface loads, but a little pop-up comes up saying “Failed to connect to the remote extension host server (Error: [invalid_argument] Error)” and the green status bar says “Disconnected from background-agent.”

Also on mac. About info:

Version: 1.7.54 (Universal)

VSCode Version: 1.99.3

Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0

Date: 2025-10-21T19:07:38.476Z (2 days ago)

Electron: 34.5.8

Chromium: 132.0.6834.210

Node.js: 20.19.1

V8: 13.2.152.41-electron.0

OS: Darwin arm64 24.6.0

I’ve been repeatedly going through the snapshot setup over the last week or so (to try to iron out some issues in my snapshot setup) and this only started recently - wednesday the 22nd or thursday the 23rd. Before that, this snapshot setup interface was pretty flakey, but I could usually get through it with only a couple retries. This new extension host failure has been consistent over maybe a dozen tries in the last 24 hours.

Hey, thanks for the report. This looks like a regression in version 1.7.54 affecting Background Agent setup. The timing and the identical error across multiple users confirm it.

I’ll pass this to the team. In the meantime, if you need Background Agent urgently, you can try:

  • Downgrading to version 1.7.53 or earlier (if available in your download history)
  • Checking for Cursor updates over the next few days, a fix may land soon

Thanks for the detailed logs and environment info, super helpful.

Thank you @deanrie.

Just to let you know, downgrading does not solve the issue.

I’m having the same problem with previous versions (1.7.53, 1.7.52, or 1.7.46).

2 Likes

Hi Carlos and Kevin, thanks for the detailed bug report, and sorry for the trouble.

We just deployed a server-side fix that should resolve the issue. Could you try again and let us know if it’s working now?

Thanks,
Anatole

I’m now able to start and connect to the Backgroud Agent Setup.

Thank you @anatolebeuzon!

1 Like

Hi, might be unrelated but on Cursor 2.0 I stopped seeing background agents.

Yep, all good - thanks!

1 Like