Devcontainer disconnects more frequent since v2.4.23

[mjnowen]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Somewhere between Cursor v2.4.23 and 2.4.31, I ma seeing much more frequent devcontainer disconnects after X amount of time AFTER I have executed something in Cursor like hit “Build” on a plan. It feels like a Cursor scheduled cleanup routine is killing old processes and decided to kill 1 or more terminals that I might have open (unrelated to Cursor) and also disconnects the actual connection to the devcontainer. A reconnect or rebuild always fixes the issue…until next time.

Steps to Reproduce

Use Cursor from within a devcontainer using a new version of v2.4.23+ and after a period of Cursor usage, the devcontainer will timeout and disconnect.

Expected Behavior

devcontainer does not disconnect due to Cursor.

Operating System

MacOS

Version Information

Version: 2.4.31
VSCode Version: 1.105.1
Commit: 3578107fdf149b00059ddad37048220e41681000
Date: 2026-02-08T07:42:24.999Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report, and I can see this was already fixed in v2.1.0. Looks like a regression.

To help the team narrow this down, could you grab the Dev Containers logs? Open the Output panel (View > Output), pick “Dev Containers” from the dropdown, and copy everything from around the time the connection drops. I’m especially interested in what shows up right before it disconnects.

Also, about how long is it between an action (like clicking Build) and the disconnect? Is it minutes, or more like an hour or longer?

I’ll pass this along to the team. I can’t promise a timeline, but the fact that this was fixed before and came back should help us track what changed.