Cursor Dev Container remoteEnv option not working

Describe the Bug

The devcontainer.json can include the option to set environment variables for the devcontainer environment, namely “remoteEnv” (see Development Container Specification). It seems like when using the cursor dev-container extension, this will get ignored, see more here:

Overall the cursor dev-container extension seems slow and unstable, i wanted to switch back to vs-code dev-container extension but its not listed on the extension marketplace…

Steps to Reproduce

Add any configuration for dev-container setup and try to use “remoteEnv” in the devcontainer.json to pass env-vars to the dev-container env

Expected Behavior

The env-vars gets set properly

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.1
VSCode Version: 1.99.3
Commit: 031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0
Date: 2025-07-03T06:06:37.704Z (2 days ago)
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

Yes - Cursor is unusable

I also have this issue. Very frustrating.

Also having this issue, have to run the vscode dev container side by side with cursor at the moment.

Hi @ungerpeter , @mrjarnould , and @Alexander_Sullivan – could you upgrade to version 1.0.9 of the Anysphere Remote Containers extension? This version adds support for remoteEnv.