starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 07:54:35 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Feature Request: Preserve Python Virtual Environment and Working Directory on "Duplicate Tab" #23322

New Issue
Closed
opened 2026-01-31 08:38:51 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:38:51 +00:00
Owner
Copy Link

Originally created by @mriamnobody on GitHub (May 31, 2025).

Description of the new feature

The current "Duplicate Tab" functionality in Windows Terminal does not fully replicate the existing session. Two critical issues are observed:

  1. Working Directory Not Preserved
    When duplicating a tab, the new tab defaults to the user’s home directory (e.g., C:\Users\Username) rather than maintaining the working directory of the original tab.

Expected Behavior:
The duplicated tab should open in the same working directory as the tab it was duplicated from — this is especially important when working across deep project structures.

  1. Virtual Environment Context Not Preserved
    If a Python virtual environment (e.g., via venv or conda) is activated in the original tab, the duplicated tab does not retain this activation. It launches a plain shell session, requiring the environment to be manually reactivated.

Expected Behavior:
The new tab should inherit the activated environment context, mirroring the exact state of the original session.

This enhancement would greatly benefit developers and power users who frequently work in isolated environments and deep directory structures. Thank you for the ongoing development and great work on Windows Terminal!

Proposed technical implementation details

No response

Originally created by @mriamnobody on GitHub (May 31, 2025). ### Description of the new feature The current "Duplicate Tab" functionality in Windows Terminal does not fully replicate the existing session. Two critical issues are observed: 1. Working Directory Not Preserved When duplicating a tab, the new tab defaults to the user’s home directory (e.g., C:\Users\Username) rather than maintaining the working directory of the original tab. Expected Behavior: The duplicated tab should open in the same working directory as the tab it was duplicated from — this is especially important when working across deep project structures. 2. Virtual Environment Context Not Preserved If a Python virtual environment (e.g., via venv or conda) is activated in the original tab, the duplicated tab does not retain this activation. It launches a plain shell session, requiring the environment to be manually reactivated. Expected Behavior: The new tab should inherit the activated environment context, mirroring the exact state of the original session. This enhancement would greatly benefit developers and power users who frequently work in isolated environments and deep directory structures. Thank you for the ongoing development and great work on Windows Terminal! ### Proposed technical implementation details _No response_
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 08:38:52 +00:00
claunia commented 2026-01-31 08:38:52 +00:00
Author
Owner
Copy Link

@achaljhawar commented on GitHub (Jun 1, 2025):

Hi can I work on this issue?

@achaljhawar commented on GitHub (Jun 1, 2025): Hi can I work on this issue?
claunia commented 2026-01-31 08:38:53 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 2, 2025):

Working Directory Not Preserved

Have you set up your shell with OSC 9;9? See here: https://learn.microsoft.com/en-us/windows/terminal/tutorials/new-tab-same-directory

Virtual Environment Context Not Preserved

The terminal has practically no idea what you're running inside your shell. (And if it did, that would be quite the violation of trust.) As such it also doesn't know about your venv.

You can create a custom terminal profile that spawns you in the right directory with the right activation.

@lhecker commented on GitHub (Jun 2, 2025): > Working Directory Not Preserved Have you set up your shell with `OSC 9;9`? See here: https://learn.microsoft.com/en-us/windows/terminal/tutorials/new-tab-same-directory > Virtual Environment Context Not Preserved The terminal has practically no idea what you're running inside your shell. (And if it did, that would be quite the violation of trust.) As such it also doesn't know about your venv. You can create a custom terminal profile that spawns you in the right directory with the right activation.
claunia commented 2026-01-31 08:38:53 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 4, 2025):

Alas, without some additional setup on your site this isn't going to be something Terminal can support.

Though if I may recommend a workaround: if you set up your virtual environment in your profile command line, duplicating a tab with that profile will carry along the venv activation. 🙂

@DHowett commented on GitHub (Jun 4, 2025): Alas, without some additional setup on your site this isn't going to be something Terminal can support. Though if I may recommend a workaround: if you set up your virtual environment _in your profile command line,_ duplicating a tab with that profile will carry along the venv activation. 🙂
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#23322
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?