Describe the Bug
Dev Container not work after switched to “Anysphere” Dev Container.
Q1: In the container startup, the “feature” section in devcontainer.json not work, it looks like can’t connect to internet, from the log, I saw the frist job after Container startup is handle the “feature” section, are you forget to handle the “containerEnv” or “build” section? I add some proxy in that, without proxy, downloading will fail.
Q2: HOW CAN I SWITCH BACK TO VSCODE DEV CONTAINER EXTENSION? I CAN NOT FIND VSCODE DEV CONTAINER IN THE MARKET ANYMORE? WHY???
Steps to Reproduce
build devcontainer fail
startup devcontainer fail
WITH “Anysphere” DEV CONTAINER
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.2.4 (user setup)
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T17:09:01.383Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045
Additional Information
“Anysphere” DEV CONTAINER
Version: 1.0.12
Hi @StudyingTime , thank you for the bug report. Can you share your devcontainer.json file so we can take a closer look? Features are generally supported, though we are looking into an issue where “remoteEnv” and “customizations” are not being applied. Features themselves do not have a build, and I was not able to reproduce an issue with containerEnv (since this is handled when building the container).
If you’re using remoteEnv in a feature, could you try switching that to containerEnv?
The original VSCode 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 this alternative version, which is actively being improved. We are aware of the issues with the experience, particularly around missing functionality, and we’re working to bridge that gap.
Hi @StudyingTime, could you try upgrading to version 1.0.14 of the Anysphere Remote Containers extension? We fixed some issues with how attributes from features were previously ignored.