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

Keeps losing lines of history #23530

New Issue
Closed
opened 2026-01-31 08:44:56 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 08:44:56 +00:00
Owner
Copy Link

Originally created by @github-account1111 on GitHub (Aug 16, 2025).

Windows Terminal version

1.22.12111.0

Windows build number

10.0.26100.0

Other Software

No response

Steps to reproduce

  1. Have a few tabs open
  2. Use the Terminal normally for a few hours
  3. Close a tab

Expected Behavior

History is saved. Commands show up when I press the Up arrow key.

Actual Behavior

This isn't consistent, but sometimes, some commands - somehow the most useful ones, ones I would want to refer back to in the future - end up missing. All that gets saved is the useless stuff like cd and ls.

I am so tired of dealing with this issue (alongside a bunch more). This never happened on Windows 10 with good ol' blue PowerShell. Sure, it was less pretty than the shiny new Windows 11 Terminal, but also far less buggy and inconsistent. Stop laying off your developers, M$. Your software quality is in the toilet right now.

Originally created by @github-account1111 on GitHub (Aug 16, 2025). ### Windows Terminal version 1.22.12111.0 ### Windows build number 10.0.26100.0 ### Other Software _No response_ ### Steps to reproduce 1. Have a few tabs open 1. Use the Terminal normally for a few hours 1. Close a tab ### Expected Behavior History is saved. Commands show up when I press the Up arrow key. ### Actual Behavior This isn't consistent, but sometimes, some commands - somehow the most useful ones, ones I *would* want to refer back to in the future - end up missing. All that gets saved is the useless stuff like `cd` and `ls`. I am so tired of dealing with this issue (alongside a bunch more). This never happened on Windows 10 with good ol' blue PowerShell. Sure, it was less pretty than the shiny new Windows 11 Terminal, but also *far* less buggy and inconsistent. Stop laying off your developers, M$. Your software quality is in the toilet right now.
claunia added the Needs-TriageIssue-BugNeeds-Author-FeedbackNo-Recent-Activity labels 2026-01-31 08:44:57 +00:00
claunia commented 2026-01-31 08:44:58 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Aug 19, 2025):

Fortunately (for us) we're a terminal - we're basically a fancy text renderer, nothing more. If I read your description right, your issue is with saving the history, which is a feature of your shell. I'm assuming you're using PowerShell, and in that case, I suggest the following:

  • Use PowerShell 7 instead of 5
  • In your Microsoft.PowerShell_profile.ps1 add Set-PSReadLineOption -AddToHistoryHandler $null which disables filtering of sensitive data from your history (if PowerShell thinks your line contains passwords, it won't save it to the history)
  • Otherwise, file an issue with the PowerShell folks over at https://github.com/PowerShell/PSReadLine
@lhecker commented on GitHub (Aug 19, 2025): Fortunately (for us) we're a terminal - we're basically a fancy text renderer, nothing more. If I read your description right, your issue is with saving the history, which is a feature of your shell. I'm assuming you're using PowerShell, and in that case, I suggest the following: * Use PowerShell 7 instead of 5 * In your `Microsoft.PowerShell_profile.ps1` add `Set-PSReadLineOption -AddToHistoryHandler $null` which disables filtering of sensitive data from your history (if PowerShell thinks your line contains passwords, it won't save it to the history) * Otherwise, file an issue with the PowerShell folks over at https://github.com/PowerShell/PSReadLine
claunia commented 2026-01-31 08:44:58 +00:00
Author
Owner
Copy Link

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

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Aug 24, 2025): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**. <!-- 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 Needs-Author-Feedback Needs-Triage No-Recent-Activity
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#23530
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?