Updates on "attach to existing container" on Dev Containers

Bug Reports
1

Describe the Bug

Has there been any updates on getting attach to existing containers on the dev containers working? That workflow would be much easier because our developers are already maintaining a container and trying to catchup and sync on the new .devcontainers is a bit difficult.

The main thing we need is the ability to attach to an existing container but using a remoteUser specification

Steps to Reproduce

  • SSH into Linux from mac
  • attach to existing container with remoteUser

Expected Behavior

attach to existing container from ssh working with remoteUser specification

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.4 (Universal)
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T16:55:16.443Z (1 wk 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

Additional Information

dev containers version 1.0.18

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

Hi @Shantanu_Jhaveri, thank you for following up here. We are currently testing an update with this functionality and are aiming to release it this week.

4

That would be great because now we already maintain 4 containers and given that we need to make .devcontainers parity for each one - we are now maintaining 2x = 8 containers and the constant changes to the extensions are breaking some of our workflows