bug(shell): terminal command detection fails on some macOS setups

[BalduinLandolt]

Bug summary

loom init configures command = "ghostty" for Ghostty terminal, but loom shell doesn't actually open a shell in Ghostty on some macOS setups. The bare ghostty command exists but doesn't launch a terminal shell — it opens a configuration/management interface instead. The workaround is manually editing config.toml to command = "open -a Ghostty".

Command

loom shell

Steps to reproduce

1. Run loom init and select Ghostty as terminal
2. Config is written as command = "ghostty"
3. Run loom shell

Expected behavior

A new Ghostty terminal opens with a shell in the workspace directory.

Actual behavior

The ghostty command runs but does not open a usable terminal shell — it launches a configuration interface instead. The correct invocation on this macOS setup is open -a Ghostty.

Note: the bare ghostty command may work correctly on some setups (e.g., Nix-managed installations). LOOM should either detect the correct invocation method or validate that the configured command actually opens a terminal.

Environment

• macOS (standard Ghostty.app installation, not Nix)

[subotic]

Closed by #69 — ghostty on macOS auto-detects .app bundle and uses open -a at runtime