# Extension Host navigator.userAgent doesn't match renderer process, breaking VS Code extension compatibility

**URL:** <https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095>\
**Category:** Bug Reports\
**Tags:** java\
**Created:** [January 6, 2026, 10:21am UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095 "2026-01-06T10:21:17Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![Srinivas\_Chunduri](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@Srinivas\_Chunduri](https://forum.cursor.com/u/Srinivas_Chunduri)\
**Post date:** [January 6, 2026, 10:21am UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/1 "2026-01-06T10:21:17Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

## Description

The `navigator.userAgent` in Cursor’s Extension Host process doesn’t contain  
platform information (e.g., “Windows”), while the renderer process does. This  
breaks VS Code extensions that use `navigator.userAgent` for platform detection.

## Root Cause

The extension checks `navigator.userAgent.includes("Windows")` before  
`process.platform`, which works in VS Code but fails in Cursor’s Extension Host.

**Developer Tools (Renderer):**

### Steps to Reproduce

## Reproduction

1. Install Oracle SQL Developer extension (oracle.sql-developer) - Have to use Install extension from VSIX method as the extension is not available from Oracle in Cursor Marketplace.
2. Extension fails to activate with: “Process terminated with exit code 1”

### Expected Behavior

Extension should be installed and activated successfully.

### Operating System

Windows 10/11

### Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.44 (system setup)  
VSCode Version: 1.105.1  
Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0  
Date: 2025-12-24T21:41:47.598Z  
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.19045

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [January 6, 2026, 4:11pm UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/3 "2026-01-06T16:11:42Z")

</div>

Hey, thanks for the report.

This is a known issue affecting the Oracle SQL Developer extension. We’re seeing similar reports from other users: [Extension Not Activated After 2.0.54 update](https://forum.cursor.com/t/extension-not-activated-after-2-0-54-update/140975)

---

<div class="post-metadata">

**Author:** ![Srinivas\_Chunduri](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@Srinivas\_Chunduri](https://forum.cursor.com/u/Srinivas_Chunduri)\
**Post date:** [January 6, 2026, 4:27pm UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/4 "2026-01-06T16:27:20Z")

</div>

Thanks for the response. Could you please let us know if this can be fixed by Cursor in the next release? We are all having troubles with this extension which is a must for our daily work.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [January 6, 2026, 4:35pm UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/6 "2026-01-06T16:35:39Z")

</div>

The bug is already being worked on by the team. The Extension Host in Cursor doesn’t pass platform info into `navigator.userAgent`, which breaks extensions that use this check to detect the platform (including the Oracle SQL Developer extension).

You can track progress in this thread, and I’ll post an update as soon as there’s news from the dev team.

---

<div class="post-metadata">

**Author:** ![jason419](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@jason419](https://forum.cursor.com/u/jason419)\
**Post date:** [January 13, 2026, 11:23pm UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/7 "2026-01-13T23:23:42Z")

</div>

Is this any update on this? I’m the original poster of thread linked to on this thread. It has been months since the issue was reported. My workaround was to continue using an older version of cursor that didn’t have this issue. Now that old cursor version will no longer interact with AI models and forces an update. So, I have no work around.

---

<div class="post-metadata">

**Author:** ![ravirahman](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ravirahman/32/20386_2.png) [@ravirahman](https://forum.cursor.com/u/ravirahman)\
**Post date:** [January 15, 2026, 5:26pm UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/9 "2026-01-15T17:26:42Z")

</div>

We are working on a fix for this and expect to have this patched in version 2.4, which should be released this month.

---

<div class="post-metadata">

**Author:** ![Salem\_Moussa](https://avatars.discourse-cdn.com/v4/letter/s/bc79bd/32.png) [@Salem\_Moussa](https://forum.cursor.com/u/Salem_Moussa)\
**Post date:** [January 23, 2026, 11:13am UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/10 "2026-01-23T11:13:21Z")

</div>

Any updates on this ? i updated to version 2.4.21 and stil cannot find the extension to work with Oracle DB MCP

---

<div class="post-metadata">

**Author:** ![Salem\_Moussa](https://avatars.discourse-cdn.com/v4/letter/s/bc79bd/32.png) [@Salem\_Moussa](https://forum.cursor.com/u/Salem_Moussa)\
**Post date:** [January 23, 2026, 11:20am UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/11 "2026-01-23T11:20:57Z")

</div>

Hello Ravi , doesn’t seem to be fixed in version \> 2.4 , is there a timeline for this ?

---

<div class="post-metadata">

**Author:** ![Henrik-MD](https://avatars.discourse-cdn.com/v4/letter/h/90ced4/32.png) [@Henrik-MD](https://forum.cursor.com/u/Henrik-MD)\
**Post date:** [January 23, 2026, 2:07pm UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/13 "2026-01-23T14:07:44Z")

</div>

Hi folks — quick success report for the **Oracle SQL Developer** extension in **Cursor**.

**Environment**

- Cursor **2.4.21** (VSCode **1.105.1** )
- Oracle SQL Developer extension **25.3.2** (installed via VSIX)

**What worked (core fix)**  
This solution comes from the Oracle forum thread here:  
[https://forums.oracle.com/ords/apexds/post/sql-developer-for-vs-code-compatibility-with-cursor-ide-5505](https://forums.oracle.com/ords/apexds/post/sql-developer-for-vs-code-compatibility-with-cursor-ide-5505)

In short: add a tiny wrapper entrypoint that removes `globalThis.navigator` before loading the extension, then point `package.json#main` to that wrapper.

**1) Backup first**  
Close Cursor, then make a copy of the extension folder:  
`C:\Users\<user>\.cursor\extensions\oracle.sql-developer-25.3.2`  
? e.g. `oracle.sql-developer-25.3.2_BACKUP`

**2) Add wrapper entrypoint**  
Create this file:  
`C:\Users\<user>\.cursor\extensions\oracle.sql-developer-25.3.2\dist\extension-entry.js`

```js
"use strict";

// Cursor workaround: remove/neutralize navigator in Extension Host
try {
  if (typeof globalThis !== "undefined" && "navigator" in globalThis) {
    try {
      delete globalThis.navigator;
    } catch (_) {
      // If delete fails (non-configurable), neutralize it
      try {
        Object.defineProperty(globalThis, "navigator", {
          value: undefined,
          configurable: true,
          writable: true,
        });
      } catch (_) {
        // last resort
        try { globalThis.navigator = undefined; } catch (_) {}
      }
    }
  }
} catch (_) {}

// Load the original extension entry
module.exports = require("./extension.js");

```

**3) Point the extension to the wrapper**  
Edit:  
`C:\Users\<user>\.cursor\extensions\oracle.sql-developer-25.3.2\package.json`

Change `"main"` to:

```json
"main": "./dist/extension-entry.js"

```

Restart Cursor (or run **Developer: Reload Window** ). After this, the extension activated normally for me again.

Heads-up: updating/reinstalling the extension will likely overwrite these files, so keep the backup / notes handy.

---

<div class="post-metadata">

**Author:** ![Deep\_M](https://avatars.discourse-cdn.com/v4/letter/d/b782af/32.png) [@Deep\_M](https://forum.cursor.com/u/Deep_M)\
**Post date:** [January 29, 2026, 1:06am UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/14 "2026-01-29T01:06:46Z")

</div>

@Henrik-MD

Do you know if this solution is compatible with the new Oracle Extension (v25.4.0)?

I followed the documented steps on a Windows PC. After completing the steps, I noticed that the extension appears to activate successfully but then disappears immediately, making it unavailable for use. It doesn’t show up in the list of active extensions, and I’m unable to interact with it through the UI.

All the logs indicate that the extension is being successfully activated, but for some reason, I am still unable to see or use it.

At this point, I am a bit stuck and unsure why it is not behaving as expected.

Any suggestions or guidance would be greatly appreciated!

---

<div class="post-metadata">

**Author:** ![Deep\_M](https://avatars.discourse-cdn.com/v4/letter/d/b782af/32.png) [@Deep\_M](https://forum.cursor.com/u/Deep_M)\
**Post date:** [January 29, 2026, 1:46am UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/16 "2026-01-29T01:46:28Z")

</div>

@ravirahman

I recall you mentioning that this issue would be addressed in an upcoming release, but I am still encountering the same problem in version 2.4.22.

Do you have an updated ETA for a permanent fix?

---

<div class="post-metadata">

**Author:** ![Srinivas\_Chunduri](https://avatars.discourse-cdn.com/v4/letter/s/41988e/32.png) [@Srinivas\_Chunduri](https://forum.cursor.com/u/Srinivas_Chunduri)\
**Post date:** [January 29, 2026, 9:28am UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/18 "2026-01-29T09:28:16Z")

</div>

Hello @Deep_M I use the shortcut that says:

Ctrl + Shift + P  
Show: SQL Developer

then it should show the SQL Developer extension.

Otherwise open a new text file and change language to oracle-plsql.

---

<div class="post-metadata">

**Author:** ![Henrik-MD](https://avatars.discourse-cdn.com/v4/letter/h/90ced4/32.png) [@Henrik-MD](https://forum.cursor.com/u/Henrik-MD)\
**Post date:** [January 29, 2026, 9:53am UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/20 "2026-01-29T09:53:19Z")

</div>

Hello @Deep_M,

or try it with “View / Open View / SQL Developer”.

---

<div class="post-metadata">

**Author:** ![Deep\_M](https://avatars.discourse-cdn.com/v4/letter/d/b782af/32.png) [@Deep\_M](https://forum.cursor.com/u/Deep_M)\
**Post date:** [January 30, 2026, 7:33am UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/22 "2026-01-30T07:33:25Z")

</div>

Thanks @Srinivas_Chunduri @Henrik-MD

I can confirm that the workaround is working as expected for latest versions.

Cursor: 2.4.23  
Oracle SQL Developer Extension for VSCode:  
25.4.0

It is a bit unusual that the extension does not appear anywhere in the editor like in VS Code. I only see the extension/ saved connections list when I explicitly open the extension from the View menu (View \> Open View \> SQL Developer), but the good think is that the extension automatically detects `.sql` files, and the connection bar opens on its own.

However, I noticed `Capacity must be a positive integer greater than zero` warning message in the status bar every time I launch Cursor. It is not effecting the functionality but I am just curious to know why this warning appears.

Any thoughts or insights would be appreciated!

![image](https://us1.discourse-cdn.com/cursor1/original/3X/7/e/7ed33c3e6bab02ffb65a0452056dfd9f710d8172.png)

---

<div class="post-metadata">

**Author:** ![Henrik-MD](https://avatars.discourse-cdn.com/v4/letter/h/90ced4/32.png) [@Henrik-MD](https://forum.cursor.com/u/Henrik-MD)\
**Post date:** [January 30, 2026, 10:07am UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/23 "2026-01-30T10:07:42Z")

</div>

Hello @Deep_M

One more practical troubleshooting tip for the Oracle SQL Developer extension in Cursor:

1. **Open the bottom panel** with **Ctrl+J**

2. Go to **Output**

3. In the **dropdown/listbox on the right** , select **“SQL Developer Log”** (or “Oracle SQL Developer …”) and check whether any log entries appear there.

If the Output channel is empty / not very helpful, it can also help to **enable trace logging** for the extension:

- Add this to your Cursor user settings file:  
`C:\Users\[username]\AppData\Roaming\Cursor\User\settings.json`

```json
"Oracle SQL Developer Extension for VSCode.logging.level": "trace",

```

Then reload Cursor (Developer: Reload Window) and re-check the **Output → SQL Developer** channel.

---

<div class="post-metadata">

**Author:** ![Deep\_M](https://avatars.discourse-cdn.com/v4/letter/d/b782af/32.png) [@Deep\_M](https://forum.cursor.com/u/Deep_M)\
**Post date:** [January 30, 2026, 9:35pm UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/25 "2026-01-30T21:35:05Z")

</div>

My hunch is that the `Maximum number of SQL History records` property in the extension configuration might be causing the warning. By default, this property is set to `0`.

I changed the value to `500`, and since then, I haven’t seen the warning message.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [February 21, 2026, 9:35pm UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/27 "2026-02-21T21:35:30Z")

</div>

Closed on February 21, 2026, 9:35pm UTC

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