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

Support Bug Reports
1

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

3

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

4

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.

6

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.

1 Like
7

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.