Extension host terminated

I just started to get this error today.

In researching, I have tried all suggestions:

  • Removing all extensions
  • Removing the workspace storagecache

Any suggestions?

Version: 2.4.0-pre.37.patch.0
VSCode Version: 1.105.1
Commit: d89c477d9c8fc5297ec6f812e2dca287b9f13cf0
Date: 2026-01-16T02:17:56.109Z
Build Type: Stable
Release Track: Default
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0

1 Like

Note, none of my MCP servers can start and no agents.

Same here
Version: 2.4.0-pre.37.patch.0 (system setup)
VSCode Version: 1.105.1
Commit: d89c477d9c8fc5297ec6f812e2dca287b9f13cf0
Date: 2026-01-16T02:17:56.109Z
Build Type: Stable
Release Track: Nightly
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

Me too, but it went back to normal after setting Update Access to Default. (Version: 2.3.35)

Hey, thanks for the report. I’ll pass it to the team.

I’m getting the same on Nightly:

Version: 2.4.0-pre.38.patch.0 (Universal)
VSCode Version: 1.105.1
Commit: 525605a4127b57a79c77fe692dd9ff06f05ece00
Date: 2026-01-16T05:38:22.133Z (1 hr ago)
Build Type: Stable
Release Track: Early Access
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0

Moving to the Early Access or Default versions resolved the issue.

Same here on the latest nightly.

Same here (I’m on nightly)

Version: 2.4.0-pre.38.patch.0
VSCode Version: 1.105.1
Commit: 525605a4127b57a79c77fe692dd9ff06f05ece00
Date: 2026-01-16T05:38:22.133Z (1 hr ago)
Build Type: Stable
Release Track: Nightly
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Same here ( on nightly)

i’m on Early Access but still has this issue

how to downgrade version?

Weird can you share your ā€œAbout Cursorā€, it should have a similar version on early access

Version: 2.3.40 (Universal)
VSCode Version: 1.105.1
Commit: 230922a103262db3487b753c8d1e0a7111c2d780
Date: 2026-01-16T04:42:17.525Z (5 hrs ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0

Did you wait for version to download and then restart cursor after switching?

I just switched back to nightly, it seems like they already patched it.

Version Info:

Version: 2.4.0-pre.41.patch.0 (Universal)
VSCode Version: 1.105.1
Commit: e62153373d5f281ae01af6e3d66e0bcef1e5e830
Date: 2026-01-16T08:27:33.020Z
Build Type: Stable
Release Track: Nightly
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0
1 Like

It works for me now
Version: 2.4.0-pre.41.patch.0 (system setup)
VSCode Version: 1.105.1
Commit: e62153373d5f281ae01af6e3d66e0bcef1e5e830
Date: 2026-01-16T08:27:33.020Z
Build Type: Stable
Release Track: Nightly
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

Grab your preferred version from here:

It’s a link collection of all recent Cursor releases

I can confirm this has been fixed.

Version: 2.4.0-pre.46.patch.0
VSCode Version: 1.105.1
Commit: 670f701690eeb27b6643eeee658d3016e0d2bb40
Date: 2026-01-17T23:37:19.378Z
Build Type: Stable
Release Track: Nightly
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0

This has returned in the following version:
Version: 2.4.13
VSCode Version: 1.105.1
Commit: 75f166b4068d17ece72a475bba8c740423b255e0
Date: 2026-01-22T01:47:09.172Z
Build Type: Stable
Release Track: Nightly
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

CleanShot 2026-01-22 at 14.01.51

1 Like

New version pushed and the issue is still there.

Version: 2.4.14
VSCode Version: 1.105.1
Commit: f46acd1f4f453807331ae59ea4c94fabd2b40640
Date: 2026-01-22T02:35:05.148Z
Build Type: Stable
Release Track: Nightly
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

2 Likes

I just updated Cursor to version 2.4.14, and I am having this problem all of a sudden. Still has the issue with extensions disabled.

Edit: See Solution Below!

Version: 2.4.14
VSCode Version: 1.105.1
Commit: f46acd1f4f453807331ae59ea4c94fabd2b40640
Date: 2026-01-22T02:35:05.148Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin x64 24.1.0

You can download version 2.3 from their website.

https://api2.cursor.sh/updates/download/golden/darwin-arm64/cursor/2.3

I fixed it by downgrading back to the version 2.3.41 installed via brew.

https://formulae.brew.sh/cask/cursor

[$]> brew install --cask cursor

2 Likes

Can confirm this is happening with all extensions disabled.

Version: 2.4.14 (Universal)
VSCode Version: 1.105.1
Commit: f46acd1f4f453807331ae59ea4c94fabd2b40640
Date: 2026-01-22T02:35:05.148Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

Just updated Cursor and am having the same issue.

Version: 2.4.14 (user setup)
VSCode Version: 1.105.1
Commit: f46acd1f4f453807331ae59ea4c94fabd2b40640
Date: 2026-01-22T02:35:05.148Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.19045