This is causing severe problem with using cursor because anysphere’s extension is not supporting postCreateCommand feature which is essential for many of our workspaces.
Seriously? You make me remove an extension that worked perfectly fine one version ago, to replace it with a shoddy implementation that doesn’t work, doesn’t run my postCreateCommand, and is just generally buggy, and then block me from rolling back to the extension that DID work?
The original Microsoft dev containers extension is currently not available in Cursor due to restrictions on how third-party extensions can be distributed through the Cursor marketplace. As a result, we’ve implemented an alternative version, which is actively being improved.
We know many of you are experiencing issues with the dev containers experience in Cursor, particularly around missing functionality, and we’re working to bridge that gap.
I knew why cursor is replacing the extension it’s essential to many. The implementation is very average but hopefully will improve, so I appreciate you guys are trying.
What’s worse is the silence around big changes that remove relied-on features, and why. Most can’t follow every Microsoft change, let alone care to.
Cursor is a development company, it works with LLM’s it takes 3 short lines to any LLM to get an explanation, we are working on Y, we will have Z out, these changes are unavoidable.
With the growing popularity Cursor doesn’t have the privilege of communicating post action like a small company can get away with, so the boring administrative stuff like communicating becomes a priority. It generates a lot less anger, and a lot more flexibility.
First you say it’s not supported, and now you say it’s licencing issue, so which is it now???
You didn’t implement an “alternative version”, you implemented a buggy self-rolled poor-man’s clone. It’s not even that it’s missing a few minor features - it’s that IT DOESN’T WORK!!! I have a completely stock standard dev container that uses a docker-compose yaml. It worked perfectly fine in Cursor with the MS extension, now with your version, it doesn’t even start, with some completely generic error “docker compose up failed”. Worst of all, you don’t even give us a way to go back to a previous way-of-work with the MS extension.
You should have warned people that uninstalling the MS extension is a non-reversible, breaking change. I would never have done it if you did.
If the problem with the extension is a stupid restriction in your extensions terms, FIX THE TERMS! There are millions of extensions in the VS-Code ecosystem, are you going to "implement alternative version"s for all of them? And break all of them too?
Pathetic. This is why I didn’t want to risk an annual sub. I’ll be letting my sub run out this month. If you don’t know how to support an IDE for professional developers, like professionals, JetBrains does.
Yes, please fix this issue. I had to rewrite the Dockerfile used in my dev container just because I switched to Cursor. I really don’t want to go through this for every project—it’s frustrating and time-consuming.
As Ravi has said, we are currently unable to offer the Microsoft version, as it is proprietary and cannot be distributed by us!
However, the team are rapidly working on a feature-full replacement at the moment.
We do apologise for any inconvenience caused, and we are actively working to get a replacement up and running soon!
