# Unable to develop VSCode extensions with Cursor. Could it be a bug? **URL:** \ **Category:** Help\ **Created:** [September 16, 2024, 11:59pm UTC](https://forum.cursor.com/t/unable-to-develop-vscode-extensions-with-cursor-could-it-be-a-bug/17062 "2024-09-16T23:59:36Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![lucianotonet](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/lucianotonet/32/5065_2.png) [@lucianotonet](https://forum.cursor.com/u/lucianotonet)\ **Post date:** [September 16, 2024, 11:59pm UTC](https://forum.cursor.com/t/unable-to-develop-vscode-extensions-with-cursor-could-it-be-a-bug/17062/1 "2024-09-16T23:59:36Z")
Only theme extensions is currently possible to develop with Cursor. I tried some reinstalls and other stuffs but nothing seems to work from my side. Demonstration: [![](https://us1.discourse-cdn.com/cursor1/original/2X/0/042f66cffdc268c138c6812a5d6551f6a5c54c14.jpeg "Unable to develop VSCode extensions with Cursor. Could this be a bug?") ](https://www.youtube.com/watch?v=KzYeaqEM-oo) I dubbed the video with elevenlabs, so sorry for any mistake. ---
**Author:** ![lucianotonet](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/lucianotonet/32/5065_2.png) [@lucianotonet](https://forum.cursor.com/u/lucianotonet)\ **Post date:** [September 18, 2024, 8:48pm UTC](https://forum.cursor.com/t/unable-to-develop-vscode-extensions-with-cursor-could-it-be-a-bug/17062/2 "2024-09-18T20:48:04Z")
So, where can I find support? Anyone? ---
**Author:** ![szurilo](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/szurilo/32/18811_2.png) [@szurilo](https://forum.cursor.com/u/szurilo)\ **Post date:** [January 7, 2025, 7:27am UTC](https://forum.cursor.com/t/unable-to-develop-vscode-extensions-with-cursor-could-it-be-a-bug/17062/3 "2025-01-07T07:27:05Z")
Same issue here. Very annoying. Do you find a solution? ---
**Author:** ![Strajk](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/strajk/32/5100_2.png) [@Strajk](https://forum.cursor.com/u/Strajk)\ **Post date:** [January 7, 2025, 8:35am UTC](https://forum.cursor.com/t/unable-to-develop-vscode-extensions-with-cursor-could-it-be-a-bug/17062/4 "2025-01-07T08:35:11Z")
for what it’s worth, i’ve ended up having same project opened in both vscode and cursor – using cursor for coding and vscode for building ¯\_(ツ)\_/¯ ---
**Author:** ![lucianotonet](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/lucianotonet/32/5065_2.png) [@lucianotonet](https://forum.cursor.com/u/lucianotonet)\ **Post date:** [January 7, 2025, 3:53pm UTC](https://forum.cursor.com/t/unable-to-develop-vscode-extensions-with-cursor-could-it-be-a-bug/17062/5 "2025-01-07T15:53:14Z")
The problem seems to be with the version of vscode engine defined by yo generator. Try change the “engines.vscode” value manually on the package.json to be the same as your Cursor/VS code. ---
**Author:** ![lucianotonet](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/lucianotonet/32/5065_2.png) [@lucianotonet](https://forum.cursor.com/u/lucianotonet)\ **Post date:** [January 7, 2025, 4:01pm UTC](https://forum.cursor.com/t/unable-to-develop-vscode-extensions-with-cursor-could-it-be-a-bug/17062/6 "2025-01-07T16:01:31Z")
Oh really? Just like me developing a Flutter app on Cursor with Android Studio opened aside just to be able to connect my physical device. Try this [Unable to develop VSCode extensions with Cursor. Could it be a bug? - #5 by lucianotonet](https://forum.cursor.com/t/unable-to-develop-vscode-extensions-with-cursor-could-it-be-a-bug/17062/5) and let us knows if it works ---
**Author:** ![szurilo](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/szurilo/32/18811_2.png) [@szurilo](https://forum.cursor.com/u/szurilo)\ **Post date:** [January 7, 2025, 8:44pm UTC](https://forum.cursor.com/t/unable-to-develop-vscode-extensions-with-cursor-could-it-be-a-bug/17062/7 "2025-01-07T20:44:58Z")
You are totally right! This engines.vscode describe the minimum VSCode version that is capable to run the extension. Below this version number the extension can start but may misbehave as in our situation. This could happen to me because I generated my extension with VSCode just a bit before I started to use Cursor, that seems to be a bit behind VSCode regarding its version number. So the solution is to simply decrease the engines.vscode down to the version that your Cursor is using. See 1.95.0 to 1.93.1 on the image. ![image](https://us1.discourse-cdn.com/cursor1/original/3X/7/e/7e7448a190071982fc7e79a562c973a72beb8fc5.png)