Open
Labels
area-terminalbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginfo-neededIssue requires more information from posterIssue requires more information from poster
Description
Does this issue occur when all extensions are disabled?: Yes/No No
I have tried to disable all installed extensions and the terminal will turn back to normal user.
what's weird is that it only happend on one project, the other projects don't have this problem.
- VS Code Version: 1.96.2
- OS Version: macOS 11.4
Steps to Reproduce:
- login a remote server as root user
- kill terminal
Metadata
Metadata
Assignees
Labels
area-terminalbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable buginfo-neededIssue requires more information from posterIssue requires more information from poster

Activity
gjsjohnmurray commentedon Jan 2, 2025
Does the
Start Extension Bisectcommand help you identify exactly which extension is causing the problem?anthonykim1 commentedon Jan 7, 2025
Thanks for filing this. @dark-souls-3
Does not using copilot chat still wrongly have you start as root user?
Meaning, is Python extension alone, and not using anything else (such as copilot chat via disabling copilot chat), can you still repro
eleanorjboyd commentedon Sep 23, 2026
🤖 Thanks for the additional context. Could you confirm whether this still reproduces on the latest VS Code and Python extension with Copilot Chat disabled, and provide the Python: Report Issue output, the Python output-channel logs from opening the affected terminal, the selected interpreter/environment manager, and the environment-variable differences you observe? Please also clarify whether this is a local terminal or a VS Code Remote session and how the root login was started. Issues marked
info-neededautomatically close after 30 days without a reply.github-actions commentedon Oct 24, 2026
Hey Anthony Kim (@anthonykim1), this issue might need further attention.
Deleted user (@ghost), you can help us out by closing this issue if the problem no longer exists, or adding more information.