Dev Container issues

Describe the Bug

Major Issue: in Dev Containers I use postCreate to install some development only applications 1 being the google-cloud-sdk which I need to then provide a key for authentication. Unlike VScode, the postCreate commands are sent to output rather than a Terminal so I can’t click the google link to input the key.
Minor Issue: I keep getting this notification “Do you want to install the recommended ‘Dev Containers’ extension from Anysphere for this repository?” even though it is already installed.
Minor issue: From WSL, The left bottom button where the name of the container is no longer showing commands like “reopen” and “rebuild” containers. I can only go through the command palette now.

Steps to Reproduce

install cursor dev containers extension

Expected Behavior

similar to vscode

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.6 (user setup)
VSCode Version: 1.96.2
Commit: 5b19bac7a947f54e4caa3eb7e4c5fbf832389850
Date: 2025-06-25T02:20:02.577Z
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.26100

Additional Information

I am using Windows WSL

Does this stop you from using Cursor

No - Cursor works, but with this issue

Another Issue: Cant log in to google cloud code inside a devcontainer. It fails right before it says success with a “localhost refused to connect.” This works with VScode

Hi @Manny1, thank you for reporting these issues:

Major Issue: in Dev Containers I use postCreate to install some development only applications 1 being the google-cloud-sdk which I need to then provide a key for authentication. Unlike VScode, the postCreate commands are sent to output rather than a Terminal so I can’t click the google link to input the key.

We’re looking at how to support this. In the meantime, would it work to authenticate via an environment variable or non-interactive process, or remove this and manually run after attaching to the container?

Minor Issue: I keep getting this notification “Do you want to install the recommended ‘Dev Containers’ extension from Anysphere for this repository?” even though it is already installed.

This will be fixed in Cursor 1.2.

Minor issue: From WSL, The left bottom button where the name of the container is no longer showing commands like “reopen” and “rebuild” containers. I can only go through the command palette now.

Hmm, could you share a screenshot? We have options to rebuild and reload the window from that corner icon.

Another Issue: Cant log in to google cloud code inside a devcontainer. It fails right before it says success with a “localhost refused to connect.” This works with VScode

This might be an issue with the port forwarding; does it work if you manually paste the authentication code after logging in?

like @Manny1 I cannot forward anymore the aws sso login callback url. it simply says This site can’t be reached 127.0.0.1 refused to connect. worked before with the microsoft extension. any suggestion to reinstall that extension since is not available anymore in the marketplace would be really appreciated.

Hi @francescod-subbyx , could you share the logs from the “Remote - Dev Containers” console so we can take a closer look?

Due to the restrictions that accompany third party extensions, we are unable to distribute the VSCode dev containers extension through the Cursor extension marketplace.

Nevermind today is working perfectly. Cannot reproduce the issue