Impossible to directly re-open a devcontainer folder

[DDorch]

Description

If one has previously worked on a devcontainer session, Positron tries to open this SSH‑remote connection, and, because the container is not running, it ends with a connection error.
By the way, if one tries to open a devcontainer through the “recent folder” items, it also results in an error.

Steps to Reproduce

1. Open a devcontainer in the IDE
2. Quit and wait the container to stop
3. Reopen the IDE

Expected Behavior

It could be cool, if the container can automatically by started before the connection trial.

Actual Behavior

The opening of the remote-SSH folder raises a connection error.

[DDorch]

It seems that it is tricky or impossible to implement this behavior while using the extension Open Remote SSH:

The Remote SSH extension owns the connection lifecycle, and there is no public VS Code API to intercept a failed Remote‑SSH connection and then “retry after start.” When the container is stopped, the Remote‑SSH connection fails before the remote window can load our extension, so there’s nothing to hook at that point.

Given that limitation, the only reliable auto‑start options are SSH‑side automation (like ProxyCommand/LocalCommand) or making users explicitly run “Open Folder in Devcontainer (SSH)” from the local workspace. That still uses Remote‑SSH for the connection; it just ensures the container is up before SSH tries to connect.