Starship prompt not starting in warp (though initializing it manually works just fine)

[pkmuldoon]

Discord username (optional)

No response

Describe the bug

It used to work, but in the last several weeks, starship is not working on start when warp opens. The last several lines of my config.fish:

zoxide init fish | source
source /opt/homebrew/opt/asdf/asdf.fish
fish_add_path /opt/homebrew/opt/libpq/bin
starship init fish | source

The prompt does not run when warp opens. However, if I manually run:

starship init fish | source

in a warp terminal, the starship prompt then works as normal. I have to do the above for each tab I open,

Expected behaviour

The starship prompt to be executed as per config.fish and the prompt to be rendered.

Screenshots

No response

Operating System

MacOS

OS Version

12.4

Shell Version

fish, version 3.5.0

Warp Version

v0.2022.06.13.09.15.stable_00

Additional context

No response

Warp Internal (ignore): linear-label:24888f54-df93-45d5-9bdd-e38f740cac19

No response

[phubbard]

I'm having a similar issue with zsh - neither manual nor automatic loading of starship works in Warp, though it does in iterm2 and Terminal.

[phubbard]

Never mind - found the documented workaround https://docs.warp.dev/features/prompt

[pkmuldoon]

Yeah, I tried that, and it used to work! But, even with that option on, starship will not start on either a new tab or when warp starts. It works fine if you start starship manually with starship init fish | source

[elviskahoro]

Will share updates as we have them. Thanks for reporting!

[pkmuldoon]

As of v0.2022.08.01.09.12.stable_02 the starship prompt now appears normally without need to run starship init fish | source manually. I wish I could point to a version/fix that made this happen, either in Warp, Starship or Fish. Thanks!

[ajbarry]

Although the original report relates to fish, I had the same issue with zsh. The prompt would not show unless I manually init it on the command-line. In my case I was coming from iTerm2 and I had its shell integration sourced deep in my dotfiles: source ${HOME}/.iterm2_shell_integration.zsh. Removing this line probably resolves a bunch of weird issues but resolving my starship prompt issues was one of them.

[0mjs]

I am in the same position with Warp, Starship and ZSH
I have removed a lot of the options from my zshrc but I'm still not seeing Starship open in Warp, I tried the first "workaround" but to no avail
Any other ideas? I like Warp, but I'll need Starship or I'll be going back to iTerm

[fevral13]

@0mjs try to comment out everything in your .zshrc, make sure Starship is working in warp, and then uncomment back line by line. This approach works in many other cases when you do not know the cause of the problem.

btw, @ajbarry 's solution worked for me. thank you @ajbarry

[ChrisTTian667]

I am in the same position with Warp, Starship and ZSH
I have removed a lot of the options from my zshrc but I'm still not seeing Starship open in Warp, I tried the first "workaround" but to no avail
Any other ideas? I like Warp, but I'll need Starship or I'll be going back to iTerm

I've the same issue on a newly installed MacOS (Apple Silicon) using Warp, ZSH and Starship with no other modules at all.
But Starship does initialize when i open the zsh manually.

[j-like-jeff]

Same problem here.

disabling iterm2_shell integration works.

iTerm2

The iTerm2 shell integration breaks Warp and your custom prompt will not be able to be visible with this on. If you're coming from iTerm please check your dotfiles for it. We advise disabling the integration just for Warp like so:

if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
##### WHAT YOU WANT TO DISABLE FOR WARP - BELOW

test -e "${HOME}/.iterm2_shell_integration.zsh" && source "${HOME}/.iterm2_shell_integration.zsh"

##### WHAT YOU WANT TO DISABLE FOR WARP - ABOVE
fi

[madcapnmckay]

I am having the same issue as @ChrisTTian667. Fresh MacOS (Apple Silicon), no iTerm, the default shell is zsh. The starship toml items mentioned here is not present for me. Has anyone got this working?

Even if I manually init in warp I don't see the prompt.

[ChrisTTian667]

I am having the same issue as @ChrisTTian667. Fresh MacOS (Apple Silicon), no iTerm, the default shell is zsh. The starship toml items mentioned here is not present for me. Has anyone got this working?

Even if I manually init in warp I don't see the prompt.

In my case, i had not Enabled the Option "Honor user's custom promot (PS1)" in the Warp Terminal settings. After enabling this option Starship worked as expected. :)

[zfalen-deloitte]

Same problem here.

disabling iterm2_shell integration works.

iTerm2

The iTerm2 shell integration breaks Warp and your custom prompt will not be able to be visible with this on. If you're coming from iTerm please check your dotfiles for it. We advise disabling the integration just for Warp like so:

if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
##### WHAT YOU WANT TO DISABLE FOR WARP - BELOW

test -e "${HOME}/.iterm2_shell_integration.zsh" && source "${HOME}/.iterm2_shell_integration.zsh"

##### WHAT YOU WANT TO DISABLE FOR WARP - ABOVE
fi

This from @j-like-jeff above works. Double check your .zshrc

[dsomel21]

Powerlevel 10k + Powershell Issues

I was having this issue, and I thought it was because of Powerlevel, but it was because of Powerline!

The Fix

In my ~/.bash_profile I had:

. /Users/dilraj/Library/Python/2.7/lib/python/site-packages/powerline/bindings/bash/powerline.sh

I updated it to:

if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
  # Powerline - Do not run in Warp.dev
  . /Users/dilraj/Library/Python/2.7/lib/python/site-packages/powerline/bindings/bash/powerline.sh
fi

Then run source ~/.bash_profile and exit and re-open your command line interfaces! Wrap is good for me now!

[madcapnmckay]

For my issue, I was just being dumb. I hadn't realized I needed to select "Use my own prompt". I dunno if I missed that in the docs or what.

[ericclemmons]

The latest version of Warp shows you a picture to choose from: