starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

"Duplicate Tab" Creates a New Tab Instead of Cloning the Current Instance #22938

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

Originally created by @marcuwynu23 on GitHub (Feb 19, 2025).

Windows Terminal version

1.21.10351.0

Windows build number

10.0.26100.3194

Other Software

✨ Issue Description

The "Duplicate Tab" feature in Windows Terminal does not correctly clone the current instance. Instead of duplicating the session with the same working directory, environment, and command history, it creates a completely new tab with a fresh session.

🎯 Expected Behavior

When duplicating a tab, the new tab should:

  1. Open in the same working directory as the original tab.
  2. Preserve the command history from the original session.
  3. Retain any environment variables or session-specific configurations.

🛠 Steps to Reproduce

  1. Open Windows Terminal.
  2. Navigate to a different directory using cd (e.g., cd C:\Projects).
  3. Run some commands (e.g., dir, echo Hello).
  4. Right-click the tab and select "Duplicate Tab".
  5. The new tab does not retain the working directory or history.

🔍 Current Behavior

  • The new tab starts in the default shell directory, not the current working directory.
  • Command history is lost, requiring users to manually retype previous commands.
  • Session-specific configurations (e.g., temporary environment variables) are not carried over.

💡 Possible Fixes

✅ For cmd.exe

Instead of starting a fresh cmd.exe, use:

start cmd /K

Steps to reproduce

  1. Open Windows Terminal.
  2. Open a new tab using a shell (e.g., cmd, PowerShell, WSL).
  3. Navigate to a different directory using cd (e.g., cd C:\Projects).
  4. Run some commands to populate the command history:
    • For cmd: 
      echo First Command
echo Second Command
    • For PowerShell: 
      Write-Output "First Command"
Write-Output "Second Command"
    • For WSL (Bash): 
      echo "First Command"
echo "Second Command"
  5. Right-click the tab and select "Duplicate Tab".

Expected Behavior

The new tab does not retain the working directory.

Actual Behavior

The command history is empty.
Any temporary environment variables or session-specific configurations are lost.

Originally created by @marcuwynu23 on GitHub (Feb 19, 2025). ### Windows Terminal version 1.21.10351.0 ### Windows build number 10.0.26100.3194 ### Other Software ## ✨ Issue Description The **"Duplicate Tab"** feature in Windows Terminal does not correctly clone the current instance. Instead of duplicating the session with the same **working directory, environment, and command history**, it creates a completely new tab with a fresh session. ## 🎯 Expected Behavior When duplicating a tab, the new tab should: 1. Open in the **same working directory** as the original tab. 2. Preserve the **command history** from the original session. 3. Retain any **environment variables** or session-specific configurations. ## 🛠 Steps to Reproduce 1. Open Windows Terminal. 2. Navigate to a different directory using `cd` (e.g., `cd C:\Projects`). 3. Run some commands (e.g., `dir`, `echo Hello`). 4. Right-click the tab and select **"Duplicate Tab"**. 5. The new tab **does not** retain the working directory or history. ## 🔍 Current Behavior - The new tab **starts in the default shell directory**, not the current working directory. - **Command history is lost**, requiring users to manually retype previous commands. - **Session-specific configurations** (e.g., temporary environment variables) are not carried over. ## 💡 Possible Fixes ### ✅ For `cmd.exe` Instead of starting a fresh `cmd.exe`, use: ```cmd start cmd /K ``` ### Steps to reproduce 1. Open Windows Terminal. 2. Open a new tab using a shell (e.g., `cmd`, `PowerShell`, `WSL`). 3. Navigate to a different directory using `cd` (e.g., `cd C:\Projects`). 4. Run some commands to populate the command history: - For `cmd`: ```cmd echo First Command echo Second Command ``` - For PowerShell: ```powershell Write-Output "First Command" Write-Output "Second Command" ``` - For WSL (Bash): ```bash echo "First Command" echo "Second Command" ``` 5. Right-click the tab and select **"Duplicate Tab"**. ### Expected Behavior The new tab does not retain the working directory. ### Actual Behavior The command history is empty. Any temporary environment variables or session-specific configurations are lost.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 08:27:53 +00:00
claunia commented 2026-01-31 08:27:54 +00:00
Author
Owner
Copy Link

@similar-issues-ai[bot] commented on GitHub (Feb 19, 2025):

We've found some similar issues:

  • #11678 , similarity score: 82%

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@similar-issues-ai[bot] commented on GitHub (Feb 19, 2025): We've found some similar issues: - #11678 , similarity score: 82% If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue. > Note: You can give me feedback by 👍 or 👎 this comment.
claunia commented 2026-01-31 08:27:54 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Feb 19, 2025):

Thanks for filing! We're going to mark this as a /duplicate of #5047

@carlos-zamora commented on GitHub (Feb 19, 2025): Thanks for filing! We're going to mark this as a /duplicate of #5047
claunia commented 2026-01-31 08:27:54 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Feb 19, 2025):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Feb 19, 2025): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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-Bug Resolution-Duplicate
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#22938
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?