VS Code Server now supports installing additional built-in extensions via VSIX. This is useful if the remote setup has VSIX files already available and you want to install them without having to reach out to the Marketplace, thereby improving the startup time. This helped GitHub Codespaces startup to be faster by ~125%.
When connected to a tunnel in vscode.dev, you can continue in VS Code Desktop with the Continue Working in VS Code Desktop command. The command can be found in the remote menu and the Command Palette.
Multiple instances of tunnels running on a machine will be deduplicated. Additional requests to Turn on Tunnel Access in the VS Code UI, or running code tunnel on the command line, monitor any existing running tunnel. These monitoring processes still allow you to stop or restart the tunnel by entering "x" or "r" respectively.
The settings remote.WSL1.connectionMethod and remote.WSL2.connectionMethod have been removed. The WSL extension now always uses the previous default wslExeProxy. We are not aware of any problems with that connection method. Please file issues against vscode-remote-release if the new method doesn't work for you.
A Dev Container lets you use a container as a full-featured development environment. The Dev Container Specification seeks to find ways to enrich existing formats with common development specific settings, tools, and configuration while still providing a simplified, un-orchestrated single container option.
You can learn more about dev containers and their spec in a new episode of the Changelog podcast.
The Dev Containers: Clean Up Dev Containers... and Dev Containers: Clean Up Dev Volumes... commands let you pick which of the stopped containers and dangling volumes to remove.
We keep working towards replacing the built-in legacy features with their updated counterparts in the contributable container features. The legacy maven, gradle and jupyterlab features are now mapped to the corresponding options on the ghcr.io/devcontainers/features/java and ghcr.io/devcontainers/features/python features.
For more information on contributing container features, see the Dev Container Features documentation.
We have dropped support for the few built-in Dev Container configurations that were sourced from the vscode-dev-containers repository and remain available there.