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

[Srinivas_Chunduri]

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

[deanrie]

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

[Srinivas_Chunduri]

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.

[deanrie]

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.

[jason419 (Jason H)]

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.

[ravirahman]

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

[Salem_Moussa (Salemoussa)]

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

[Salem_Moussa (Salemoussa)]

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

[Henrik-MD (Henrik)]

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

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

"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:

"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.

[Deep_M (Deep)]

@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!

[Deep_M (Deep)]

@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?

[Srinivas_Chunduri]

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.

[Henrik-MD (Henrik)]

Hello @Deep_M,

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

[Deep_M (Deep)]

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!

[Henrik-MD (Henrik)]

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

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

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

[Deep_M (Deep)]

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.