Allow forwarding privileged ports in VSCode Desktop
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe
Using VSCode Desktop, workspace listen ports less than 8000 are assigned a free high-numbered port on the local machine, instead of being mapped to the same port number as the workspace.
Describe the behaviour you'd like
Privileged ports opened in a workspace are assigned the same port number locally, if it's free.
Describe alternatives you've considered
This is supported in local-companion if you run it via sudo.
In Codespaces, this works by prompting you inside VSCode to elevate your permissions, allowing it to bind the desired port.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the VSCode Desktop port-forwarding path and compare it with the local-companion behavior described in the issue. The work is done when an available privileged workspace port is exposed locally with the same port number, with an appropriate permission-elevation flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- desktop, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100