## What happened

`SUPER + RETURN` (`omarchy-launch-terminal`) is documented as opening a terminal in the active terminal's current directory. With Ghostty — Omarchy's default terminal — it instead opens in whichever directory the *most recently spawned* shell happens to be in, regardless of which window is focused.

In practice every new terminal opened in the same unrelated project directory for me, no matter which Ghostty window I pressed the binding from.

## Expected

New terminal opens in the focused terminal's working directory.

## Root cause

`omarchy-cmd-terminal-cwd` resolves the shell by walking the children of the focused window's pid:

```bash
terminal_pid=$(hyprctl activewindow | awk '/pid:/ {print $2}')
...
  shell_pid=$(pgrep -P "$terminal_pid" | tail -n1)

  if [[ -n $shell_pid ]]; then
    cwd=$(readlink -f "/proc/$shell_pid/cwd" 2>/dev/null)
```

That assumes one process per terminal window. Ghostty's packaged desktop entry hardcodes single-instance mode:

```
$ grep Exec= /usr/share/applications/com.mitchellh.ghostty.desktop
Exec=/usr/bin/ghostty --gtk-single-instance=true
```

So every Ghostty window is hosted by a single process. `hyprctl activewindow` returns that same pid for all of them, and `pgrep -P … | tail -n1` picks the newest child shell, which has nothing to do with focus:

```
$ hyprctl clients | grep -E "class: com.mitchellh.ghostty" -B2 | grep pid:
        pid: 5081
        pid: 5081
        pid: 5081

$ for p in $(pgrep -P 5081); do echo "$p  $(readlink /proc/$p/cwd)"; done
5163     /home/user/src/alpha/app
12740    /home/user/src/alpha
481411   /home/user/src/alpha/server
573292   /home/user/src/alpha
1127008  /home/user/src/beta        <- tail -n1 picks this one
```

(paths genericized; nothing else changed)

The script already handles this correctly for kitty, querying its control socket for the genuinely focused window:

```bash
if [[ -S $kitty_socket ]]; then
  cwd=$(kitten @ --to "unix:$kitty_socket" ls --match "state:focused" ...
```

Ghostty has no equivalent branch, so it always falls through to the pid-walking path that single-instance mode breaks.

## Reproduction

1. Default Omarchy setup (`~/.config/xdg-terminals.list` → `com.mitchellh.ghostty.desktop`).
2. Open two Ghostty windows and `cd` them to different directories.
3. Focus the **first** window, press `SUPER + RETURN`.
4. The new terminal opens in the **second** window's directory.

`omarchy-cmd-terminal-cwd` can be run directly to see the resolved path without opening a window.

## Notes

Ghostty exposes no kitty-style control socket, so the fix is not a drop-in mirror of the kitty branch. Options might be reading the focused window's title (Ghostty sets it to the cwd via shell integration, but only when sitting at a prompt), or not passing `--gtk-single-instance=true` in the desktop entry Omarchy ships.

Happy to test any approach on this machine.

## System

- Omarchy `4.0.0-1`
- Ghostty `1.3.1-2`
- Hyprland `0.56.2-1`