This plan captures our work in March 2023. We follow the same iteration cycle as VS Code. Although we plan for a whole iteration, we may not only ship at the end of an iteration but throughout.

Plan Items

Below is a summary of the top level plan items.

Dev Container Specification / CLI

• 💪 Transform maven, gradle and jupyterlab usages to their features v2 counterparts cli#461 @chrmarti

Dev Containers Extension

• Remove dependance on built-in repository configs vscode-remote-release#7532 @chrmarti
• Improve management of Dev Containers vscode-remote-release#7720 @chrmarti
• 💪 Attach to Kubernetes: Support container metadata vscode-remote-release#7880 @chrmarti

Remote-SSH

• Refresh recently used folders when making edits in other windows vscode-remote-release#8100 @eleanorjboyd

Remote Repositories

• 🏃 Support committing Git LFS files from web vscode-remote-repositories-github#7 @joyceerhl
• Improvements to the GitHub Repositories extension query @joyceerhl
• 💪 Support .gitignore vscode#172643 @joyceerhl

Remote-Tunnel

• CLI invocations should connect to the running CLI process vscode#171520 @connor4312
• Adopt CLI service mode in "Turn on Remote Tunnel Access" vscode#171520 @aeschli
• Allow to open vscode desktop when connected to a tunnel on vscode.dev vscode-remote-release#8199 @aeschli

Deferred

• Fix password prompt on folder open vscode-remote-release#6227 @eleanorjboyd @roblourens
• Attempt reconnection following device short sleep vscode-remote-release#5755 @eleanorjboyd
• Reload remote explorer when editing ssh config vscode-remote-release#7144 @eleanorjboyd
• Support "Allow Tunnel access" for the remote when connected to a SSH/WSL remote window vscode-remote-release#7865 @aeschli @connor4312
• Explore adopting the CLI for starting/managing the VS Code Server on WSL vscode-remote-release#7864 @aeschli @connor4312