Ports tunnel status in Ports view not reflect immediately
Open
Nobody has claimed this yet.
editor: code (browser)
editor: code (desktop)
meta: never-stale
team: IDE
type: bug
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
Need to refresh window to make UX update
See also [tunnel with remote explorer]
Steps to reproduce
- Open workspace with VSCode Desktop
- Check tunnel icon (eyes) with local-companion
Expected behavior
UX update
Anything else?
Don't know if I did it wrong, but seems tunnel with all interface not works for me
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
Reproduce this in VSCode Desktop by opening a workspace, checking the Ports view, and observing the tunnel icon with local-companion. Read the linked remote-explorer context and trace how tunnel status reaches the Ports view. Done means the UX updates without refreshing the window, including the reported tunnel behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- desktop, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100