ghostty cli not added to path despite installed shell integration (zsh)

[dlo]

Hi all! I can't figure out what I'm doing wrong here. I wanted to play around with themes and calling ghostty +list-themes failed right away. Also running the default config.

Setup:

• macOS 15.2 (24C101)
• zsh 5.9

My .zshrc has this snippet from the docs:

if [[ -n $GHOSTTY_RESOURCES_DIR ]]; then
  source "$GHOSTTY_RESOURCES_DIR"/shell-integration/zsh/ghostty-integration
fi

The resources directory is defined:

~ $ echo $GHOSTTY_RESOURCES_DIR
/Applications/Ghostty.app/Contents/Resources/ghostty

But the ghostty cli isn't added to the PATH.

~ $ ghostty
bash: ghostty: command not found

Any ideas?

#1372

[rhodes-b]

can you run this echo $GHOSTTY_BINARY_DIR

[dlo]

~ $ echo $GHOSTTY_BINARY_DIR

~ $ echo $GHOSTTY_BIN_DIR
/Applications/Ghostty.app/Contents/MacOS

[dlo]

For what it's worth, running source $GHOSTTY_RESOURCES_DIR/shell-integration/zsh/ghostty-integration explicitly doesn't seem to work either.

[dlo]

Thanks.

Just for confirm, here's an example of what I'm referring to. The existing $PATH isn't being wiped. Sidenote: I'm surprised that more folks aren't running into this since this sort of path manipulation is quite common!

# >>> juliaup initialize >>>
# !! Contents within this block are managed by juliaup !!
export PATH="$HOME/.juliaup/bin:$PATH"
# <<< juliaup initialize <<

[rhodes-b]

Yeah can you try commenting it out and seeing if it is working

[dlo]

@rhodes-b Re: addressing the root cause, in order for this to work I would need to remove all changes to the path anywhere in my shell config?

FWIW, I don't think that's feasible but just want to understand. If that's the case, we can close this discussion, even though I think it's not ideal behavior.

[rhodes-b]

I dont know the full way shell integration works but it is known that doing specific things like appending to the path can break stuff. Might be possible to fix might not be im not the expert there

[dlo]

@rhodes-b Nailed it! It was a single line where I was setting the path explicitly.

Appreciate your help.

[thuvasooriya]

Make sure the shell you're using is zsh.

Try adding the $GHOSTTY_BIN_DIR to path manually.

If it works then the variables are being unloaded somewhere in your config.

[dlo]

Yup, confirmed. Using zsh.

Adding to the path manually works, which is expected. What do you mean by "the variables are being unloaded somewhere in your config"?

[thuvasooriya]

sorry i should've been more clear. explicit path setting unloads previous PATH settings. This sometimes happens automatically when using certain devshell environments. glad you found the solution