Hey, quick update — I just found a related Cursor thread that seems very relevant:
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.