Ghostty shell integrations fail because executable is named supacode

[pacificleo]

Please do not open a pull request yet. A maintainer reviews the report and adds the ready label once it is confirmed.

What happened?

When using Ghostty's shell integrations (like ssh-cache), commands like ssh fail with ssh:4: no such file or directory.
This happens because Ghostty's shell integration scripts hardcode the binary name as "$GHOSTTY_BIN_DIR/ghostty". However, the Xcode build creates the binary named supacode. As a result, the wrapper function fails to find the ghostty executable.

Steps to reproduce

1. Enable shell-integration-features = ssh-terminfo,ssh-env in ~/.config/ghostty/config.
2. Start a new Supacode terminal session.
3. Run ssh <any_host>.
4. See the no such file or directory error on line 4.

Supacode version and build

0.10.9

macOS version

macOS 26.4

System locale

en_US

Are you planning to fix this yourself?

• I intend to open a pull request once this is confirmed and marked ready.

Before submitting

• I searched existing issues and this is not a duplicate.
• I am on the latest available version of Supacode.
• I understand pull requests are closed until the issue is marked ready.
• I agree to follow this project's Code of Conduct.

[github-actions]

Thank you for filing this. A maintainer will review it and follow up here.

Please do not start any work or open a pull request until this issue is labeled ready. That label is a maintainer's go-ahead: a pull request opened against an issue that is not yet ready is labeled invalid until then. You will get a comment here the moment it is marked ready.

See CONTRIBUTING.md for the full flow.