DevContainer stuck at v0.327.0 (>11 months old, >10 release versions behind)

Discussions
1

In Cursor v0.42.4, the newest VS Code Extension: “DevContainer” that it is allowing me to use is v0.327.0, which is >11 months old, missing loads of bug-fixes/features, compared to the latest pre-release: v0.390.0 or GA release: v0.388.0 (>10 versions newer), combined with VS Code v1.95.1.

The lack of being able to use some of the latest VS Code extensions is causing me quite a bit of friction. Can anything be done to improve this situation in Cursor?

3 Likes
2

Unfortunately, I’m facing the same issue. I wasn’t able to update it, so I performed a manual installation, but then every functionality of the extension stopped working. I can’t open the container or the config files…nothing

This is really blocking since the actual version 0.327 does have some issues, in my case :

So I hope the cursor team can see this and help us out.

Screenshot 2025-01-02 at 11.17.55
Screenshot 2025-01-02 at 11.17.551834×296 49.3 KB

2 Likes
3

Same kind of issues here. Please update to a version that’s <3 months old

4

Hey, our next update bumps the base version of VS Code that Cursor is based off, so I would assume the Dev Containers extension would get an upgrade with it (just a guess though!)

1 Like
5

Thank you Dan! Great news.
That would indeed very likely be the case. What would be the expected timeline for this?

6

Our next update should start rolling out in the next few days, and should be available to every user by the end of next week at the latest (if we hit any bumps or bugs we need to fix first!)

7

Thank you! Indeed it’s finally working natively with Cursor 0.45+, as Dev Containers has been updated by bumping their VSCode fork version.

1 Like
8

Looks like this has resurfaced. The extension is now at 0.417.0 which reports
Unable to install extension 'ms-vscode-remote.remote-containers' as it is not compatible with VS Code '1.96.2'
Is there another update of the base VSCode version incoming soon?

10

Hi @Shaun_Lowry, we have released our own Dev Containers extension. The latest version of the VSCode extension isn’t compatible with Cursor.

image
image1098×267 20.8 KB

11

Unfortunately, this extension is missing functionality that is critical for us e.g. cloning a repo into a volume

1 Like
13

+1 the Anysphere devcontainer extension is now stuck in a perpetual loop chasing the latest feature or bug fix from the dedicated MSFT devcontainer/remote-ssh team, ultimately delivering a poorer customer experience than just getting the current MSFT owned devcontainer extension fixed/working with Cursor moving forwards.

1 Like
15

Hi @Shaun_Lowry and @mjnowen thank you for this feature request. It is on our roadmap to implement support for docker volumes and cloning remote repos. I expect this to be out in version 1.0.9 / 1.0.10 of the extension – I can’t commit to a timeline, but hopefully it’ll be out sometime this week.

Please let us know if there is any additional functionality we should prioritize.

1 Like
16

The single biggest issue is stability. The internet is a wasteland of PTY host issues with Cursor.

Common Issues with PTY Host in Cursor

  • Timeouts and Disconnections: Users have reported that after using features like Agent or Ask, all open terminals in Cursor may lose connection or timeout, especially in development container environments. This may be due to aggressive cleanup routines or process management bugs that terminate PTY sessions prematurely5.

  • PTY Host Errors with Long Scripts: Running long or resource-intensive scripts (notably in R) can trigger “pty host” errors, particularly on macOS. This interrupts analytical workflows and forces users to break tasks into smaller chunks67.

  • Unresponsive PTY Host: When running multiple or large code blocks (e.g., loading/manipulating large dataframes in R), the PTY host can become unresponsive, especially on certain hardware or OS configurations7.

  • Orphaned Processes and High CPU Usage: On remote connections (e.g., SSH to a server), Cursor may leave behind orphaned bash processes tied to the PTY host, causing high CPU usage even after the editor is closed. This indicates issues with process cleanup and resource management4.

1 Like
18

Any news on this? We’re currently pushing users back to VSCode/CoPilot to get around this

20

Also stuck on this issue. Is there even a workaround we could employ for the time being?

22

@timkooi and @Shaun_Lowry, we are aiming to have an update with Docker Volume support out next week.

3 Likes