Repository navigation
any command with 'secret' doesnt get saved in history, even though no secrets exposed. #5108
Description
ran a command with 'secrets' and found that it doesnt get stored in history.
what idiot or bot thought it would be a good idea to do this stupid shit? it wasnt a problem before. imagine all the people's
time youve wasted bc they're left guessing why the fuck their command isnt in the history, as if they're supposed to just know.
PSReadLine/PSReadLine/History.cs
Line 666 in e266ca6
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues, especially the pinned issues.
Exception report
Screenshot
N/A
Environment data
PS Version: 7.4.13Steps to reproduce
run echo 'secret' and close the tab and start new and hit up arrow or look at ConsoleHost_history its not there, but not echo 'secre'
Expected behavior
command should be in history. there's no fucking secret in the command, just the string.
Actual behavior
not in history
Activity
dAu6jARL commentedon May 16, 2026
I found like this issue.
In PowerShell 7.6.1, any command including case-insensive "token" can't be saved to (Get-PSReadLineOption).HistorySavePath.
sharpchen commentedon Jun 28, 2026
That's intentional, see:
PSReadLine/PSReadLine/History.cs
Lines 116 to 118 in ac69010
I should be able to override with https://learn.microsoft.com/en-us/powershell/module/psreadline/set-psreadlineoption?view=powershell-7.6#example-7-use-historyhandler-to-filter-commands-added-to-history