feat: 🧱 Enable terminals for additional vscode Remote Host Types #5813
+3
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Activate terminals for additional allowed VsCode Remote Host Types.
Checklist
Screenshots
[ For visual changes, include screenshots. Screen recordings are particularly helpful, and appreciated! ]
Tests
I have tested these changes locally, and in a WSL environment on windows 11. Note you can force the extension host to run in WSL by updating the vscode settings for the extension and adding the following:
Summary by cubic
Enabled terminal commands on more VSCode remote host types, including WSL, SSH, Codespaces, and containers. This allows users to run terminal commands in a wider range of remote development environments.