#PowerShell missing from Warp’s startup shell options

16 messages · Page 1 of 1 (latest)

oak socket
#

Is PowerShell (PS) supposed to appear as an option in the list of startup shells after installation?

I installed PS via Homebrew at /opt/homebrew/bin/pwsh, following the instructions in the Warp getting-started guide (https://docs.warp.dev/getting-started/using-warp-with-shells). However, PS doesn’t show up in the shell menu—I have to manually add it as a custom option.

The documentation states: “You can either make pwsh the default shell for only Warp, from the session settings (Settings > Features > Session).”

I haven’t set PS as the default shell, since I frequently switch between zsh and PS. Launching PS by typing pwsh in zsh doesn’t provide the same experience as opening it in a new session (tab).

image.png
split pivotBOT
#

Hi @oak socket. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

Based on the information provided in the knowledge sources, it appears that PowerShell (pwsh) should indeed be available as an option in Warp's startup shell settings after installation. However, your experience suggests there might be an issue or a discrepancy between the documentation and the current implementation.

According to the Warp documentation (https://docs.warp.dev/getting-started/using-warp-with-shells#using-powershell-pwsh-with-warp-on-macos), PowerShell is supported as a startup shell option. The documentation states that you can set pwsh as the default shell for Warp in the session settings (Settings > Features > Session).

However, it's worth noting that PowerShell support in Warp is a relatively recent addition. The Warp changelog (https://docs.warp.dev/getting-started/changelog#id-2024.09.26-v0.2024.09.24.08.02) indicates that PowerShell support was officially added in version v0.2024.09.24.08.02, released on 2024.09.26. If you're using an older version of Warp, this could explain why PowerShell is not appearing as an option.

Your experience of having to manually add PowerShell as a custom option suggests that there might be an issue with Warp detecting your PowerShell installation. This could be due to various factors, such as the specific version of Warp you're using or how PowerShell was installed.

Regarding your observation about launching PowerShell by typing pwsh in zsh not providing the same experience as opening it in a new session, this is expected behavior. The Warp GitHub issue (https://github.com/warpdotdev/Warp/issues/4199) mentions that "pwsh warpification isn't supported at this time. You can still run pwsh, but Warp features (i.e. Blocks, autocomplete, etc.) won't work within that session and it'll run similar to in a normal terminal."

#

To resolve this issue and get the full Warp experience with PowerShell, you should:

  1. Ensure you're using the latest version of Warp that supports PowerShell.
  2. If PowerShell still doesn't appear in the startup shell options, you may need to report this as a bug to the Warp development team.
  3. For the best experience, use PowerShell by setting it as the startup shell in Warp's settings, rather than launching it from within another shell session.

If the problem persists, it would be advisable to reach out to Warp's support team or create an issue on their GitHub repository to report this discrepancy between the documentation and your actual experience.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@oak socket Kapa.ai is still learning and improving, please let me know how I did by reacting below.

oak socket
#

I'm using Warp v0.2024.12.03.08.02.stable_04 and powershell v7.4.6

arctic edge
#

Warp doesnt list any homebrew installed shells on there (bash, zsh, or pwsh) so you're correct that you need to use the custom option to add pwsh.

Just add /opt/homebrew/bin/pwsh on there to set as default, then you can run zsh in a subshell for those sessions when you need it. Add the following line to the end of your ~.zshrc to automatically warpify the zsh subshell sessions.

# For zsh subshells, add to ~/.zshrc.
printf '\eP$f{"hook": "SourcedRcFileForWarp", "value": { "shell": "zsh"}}\x9c'
oak socket
#

Thanks!

west vigil
#

Is there an update to have powershell as an option that doesn't require it to be the default shell. I am running 0.2025.03.26.08.10.02 on MacOS.

arctic edge
#

Hey @west vigil powershell should now show up on the list of Startup shells, even if it's installed via homebrew. Running which -a pwsh should show you the location in case you need to set the startup shell to Custom.

CleanShot_2025-03-31_at_14.15.06.png
west vigil
#

@arctic edge I am assuming I am running the latest version of Warp for MacOS. I don't see it in options. Should I write a github issue for this?

image.png
#

I do not want to add it as a default shell for new tabs.

arctic edge
#

That depends, I installed powershell with brew install powershell did you install with another method?

What is the result when you run which -a pwsh ; brew list | grep -E "powershell"?

west vigil
#

/opt/homebrew/bin/pwsh
powershell

#

I did install it via homebrew