Windows: Is it possible to use pwsh instead of PowerShell?

[MetaITDev]

question

I edited the file:
C:\Users\username\AppData\Roaming\herdr\config.toml

[update]
channel = "preview"

[terminal]
default_shell = "pwsh"
shell_mode = "auto"

However, the changes don't seem to take effect. When I open a new tab, it still uses PowerShell instead of pwsh.

context

No response

[gursuj]

I managed to get it working via this:

[terminal]
default_shell = "C:\\Program Files\\PowerShell\\7\\pwsh.exe"

[HeyItsGilbert]

I was able to use the following:

[terminal]
default_shell = "pwsh"

This will allow you to use pwsh regardless of your OS. I would suspect this follows typical Path enumeration so I'd check if pwsh is in your path if it doesn't work.

I actually came here to see if we should push for it to be the default. Preferring pwsh (and frankly pushing it as the standard) will alleviate some of the maintenance burdens. Pwsh is cross platform and reduces the complexity for having to support Windows specific bits. It handles path resolution accurately across OS's. (e.g. C:/Program Files/blah is fine). Windows PowerShell (powershell.exe) is essentially only seeing extremely rare bug fixes. The PowerShell team will only be focusing on improve Pwsh.

[gursuj]

Yes, I agree that pwsh is great but doesn't it require manual installation on a vanilla Windows setup? Granted, a power user using herdr would probably have it installed but still. Maybe just check if it's installed during herdr install, and set the default accordingly?

I had some issues getting herdr to recognize the $EDITOR variable on windows, but might not have been doing things properly. I remember zellij correctly used pwsh so might be worth looking into how they handle it too.

[HeyItsGilbert]

Yea, I think a pwsh with fallback to powershell works. Microsoft is no longer shipping PowerShell.exe changes (beyond CVE's) and all the improvements that are worth while will be in pwsh. In PowerShell you probably want to set $env:EDITOR.

[byte2pixel]

My issue is that PSReadLine is not working. Not having history is a bit annoying.

I haven't figured out why it doesn't work. It's loaded the commands work like Get-History and the history save path. it works fine outside of herdr launching in Terminal, WezTerm etc.

[HeyItsGilbert]

My issue is that PSReadLine is not working. Not having history is a bit annoying.

I haven't figured out why it doesn't work. It's loaded the commands work like Get-History and the history save path. it works fine outside of herdr launching in Terminal, WezTerm etc.

When an instance of powershell starts it sets an environment variable $env:PsModulePath. If you have an application between two different version calls the environment variable is still set which causes it to load the wrong modules. E.g. powershell -> herdr -> pwsh. You'll want to launch from a consistent version. I'll find the issue on the powershell repo when I have a chance. Looks like this is being marked as a known issue and the docs are being updated with guidance 😮‍💨. PowerShell/PowerShell#27774 (comment)

[hwilsonnn]

If you have powershell installed through winget or as a Windows App, then the path will look slightly different:

[terminal]
default_shell = "C:\\Program Files\\WindowsApps\\Microsoft.PowerShell_7.6.4.0_x64__8wekyb3d8bbwe\\pwsh.exe"

After updating the config you'll then need to run herdr server reload-config as per https://herdr.dev/docs/configuration/#reload-config.

[HeyItsGilbert]

Did using just pwsh.exe not work? I ask because the MSIX version is going to become the standard and it's pretty important that pwsh shows up in the PATH.

[hwilsonnn]

You're correct, looks like pwsh.exe just works. I suspect the missing step for me was to actually reload the config.

[byte2pixel]

As far as I know I'm launching WezTerm set to use pwsh.exe, then launching herdr, which is pwsh. Both are using my $PROFILE where the module load is. Maybe that is the issue just pwsh -> herdr -> pwsh

…

On Tue, Aug 25, 2026, 21:07 Gilbert Sanchez ***@***.***> wrote: My issue is that PSReadLine is not working. Not having history is a bit annoying. I haven't figured out why it doesn't work. It's loaded the commands work like Get-History and the history save path. it works fine outside of herdr launching in Terminal, WezTerm etc. When an instance of powershell starts it sets an environment variable $env:PsModulePath. If you have an application between two different version calls the environment variable is still set which causes it to load the wrong modules. E.g. powershell -> herdr -> pwsh. You'll want to launch from a consistent version. I'll find the issue on the powershell repo when I have a chance. — Reply to this email directly, view it on GitHub <#892?email_source=notifications&email_token=AHQZUTMUVEVYPARJNLVUSGL5LZA47A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRGU2TSMBVUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18155905>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHQZUTLHB4SFFL4YWYCTSAT5LZA47AVCNFSNUABJKJSXA33TNF2G64TZHMYTCOJTHEYDSMBVGA5UI2LTMN2XG43JN5XDWMJQGM2DINZSG6QXMAQ> . You are receiving this because you commented.Message ID: ***@***.***>

[HeyItsGilbert]

Following up on #892 (reply in thread)

I would compare what your $env:PSModulePath looks like throughout. You might also want to see what $PROFILE.CurrentUserCurrentHost looks like. $PROFILE is actually a set of different profiles that are loaded (if they exist) in particular order. Sometimes that can have unintended consequences (but can usually be helpful). about_profiles

[byte2pixel]

Noted:
Once starting herdr this path is missing:
c:\program files\powershell\7\Modules

Before starting herdr (newlines added for easier reading.

C:\Users\xxxxx\OneDrive\Documents\PowerShell\Modules;
C:\Program Files\PowerShell\Modules;
c:\program files\powershell\7\Modules;
C:\Program Files\WindowsPowerShell\Modules;
C:\Windows\system32\WindowsPowerShell\v1.0\Modules

Once running, herdr, the 3rd one is missing, and the other 4 are still present. That probably explains it.

CurrentUserCurrentHost is this just in WezTerm->pwsh.exe and in herdr

C:\Users\xxxxx\OneDrive\Documents\PowerShell\Microsoft.PowerShell_profile.ps1

I'm inclined to believe it has something to do with the PSModulePath missing c:\program files\powershell\7\Modules;

[JJLiebig]

#4297 now defaults to pwsh (PowerShell 7) if it's on PATH on Windows. Thanks for the discussion here!