After update to 2.0.54 my extension “Oracle SQL Develope Extension for VSCode” is stuck while activating. The extension has a message displayed at the bottom status bar that says “Activating Oracle SQL Develope Extension for VSCode…” which normally takes 5-10 seconds. It has been stuck for 1 hour today.
Extension Details:
Oracle SQL Developer Extension for VSCode
Identifier: oracle.sql-developer
Version: 24.4.1
Last Updated: 2024-12-20, 22:30:56
Steps to Reproduce
Restart Cursor, wait for activation
Expected Behavior
Extension activates in 5-10 seconds and I can start using it.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
This continues to not function in the following version of Cursor. I also noticed that the extension no longer appears in the Extensions marketplace in Cursor. I downloaded the VSIX for version 25.1.1 from VSCode’s marketplace, this is the lastest version that is compatible with VSCode Version: 1.99.3. This newer version of the Oracle extension also does not work.
If there’s anything else I should try please let me know. I see that I’m one of a few that is using this extension with Cursor (at least that comes to this forum), but this has a heavy impact on my workflow. I’m back in VSCode because running queries and seeing results in my IDE is far more important that AI tasks. I’m now performing AI tasks on chatgpt.com and pasting back and forth. It’s like 2024 again, lol.
I added trace logging and found that DBToolsServerApp is being terminated within a few seconds of spawning. Some investigation mostly with AI chats suggest that its a sandboxing issue (but this is not my area and AI is not always accurate).
Thanks for posting! That’s unfortunate, I was really banking on this working once the base VSCode version was updated. This extension is important to my workflow, so I downgraded to Cursor 1.7.54 a few weeks ago. The SQL functionality is far more important than slightly improved AI workflows.
I posted this to Oracle as well, but they don’t support it because it isn’t VSCode. I’m not sure where to go since it is so niche that Cursor will probably not get to it and the extension developer doesn’t support it.
We have been using the paid version of Cursor for a couple of months now and have migrated from Visual Studio Code. We have seen the issue degrade with every new update of the Cursor IDE. At the moment we are at a state where the extension is completely unusable within Cursor, which is a pity; given the effort and work made to create this IDE.
Just following up on this — since that post the Cursor IDE has moved on (now around version 2.3.41 according to recent releases and changelogs), and the Oracle SQL Developer Extension also got a fresh release (v25.4.0) with its own updates.
Given that the previous report showing activation failures with 25.3.2 on a newer VSCode base was very useful… I’m curious:
Has anyone tried installing the SQL Developer Extension (v25.4.0) in Cursor 2.3.41 yet, and if so, have you had any success getting it to activate and run normally?
Specifically:
Does the extension start and keep the DBTools server process running?
Or does it still terminate with an error (like with 25.3.2) when activating in Cursor?
Would be great to know if this combination now works for Oracle connectivity in Cursor — thanks!
According to that discussion, the activation issue is a known problem in Cursor’s extension host (incorrect navigator.userAgent), and a fix is planned for Cursor version 2.4, potentially later this month.
If that lands as expected, there’s a good chance extensions like Oracle SQL Developer may finally activate correctly again. Fingers crossed — that would be great news.
Humm this is a real problem . I read from a cursor developer that issue would be fixed on version 2.4 so I updated and on verstion 2.4.21 but still no fix . Extension not found . Cannot work with Oracle DB MCP . Any suggestion would be helpful.
Thanks all — I managed to get the Oracle SQL Developer extension working again in Cursor, and I wrote up the fix + steps here (incl. the navigator.userAgent / wrapper entrypoint workaround):
Has anyone tried installing the SQL Developer Extension (v25.4.0) in Cursor 2.3.41 yet, and if so, have you had any success getting it to activate and run normally?