Triggering quick terminal on macos will not focus on ghostty

[Lozgemk]

Issue Description

When triggering the quick terminal in macOS, the activated app, as can be seen from the menu bar, is not Ghostty. This is different from iTerm2's hotkey window implementation. An issue I'm facing with this is that if I then use Raycast's clipboard history to paste something, it's pasted to the activated app instead of Ghostty.

Expected Behavior

Ghostty is activated (as the app shown in the menu bar) when the quick terminal is triggered.

Actual Behavior

The app that was being used before triggering the quick terminal is still activated.

Reproduction Steps

1. Focus on an app, e.g., chrome.
2. Trigger quick terminal.

Ghostty Logs

No response

Ghostty Version

Ghostty 1.2.1-main+16026f302

Version
  - version: 1.2.1-main+16026f302
  - channel: tip
Build Config
  - Zig version   : 0.15.1
  - build mode    : .ReleaseFast
  - app runtime   : .none
  - font engine   : .coretext
  - renderer      : renderer.generic.Renderer(renderer.Metal)
  - libxev        : kqueue

OS Version Information

MacOS 26.0.1

(Linux only) Display Server

None

(Linux only) Desktop Environment/Window Manager

No response

Minimal Ghostty Configuration

keybind = global:ctrl+`=toggle_quick_terminal
quick-terminal-animation-duration = 0
quick-terminal-screen = macos-menu-bar
quick-terminal-autohide = false

Additional Relevant Configuration

No response

I acknowledge that:

• I have reviewed the FAQ and confirm that my issue is NOT among them.
• I have searched the Ghostty repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.
• I have checked the "Preview" tab on all text fields to ensure that everything looks right, and have wrapped all configuration and code in code blocks with a group of three backticks (```) on separate lines.

[mitchellh]

This is currently working as designed, so this isn't a bug, though I understand your arguments. I think we need more research done on unearthing why we chose this approach (I think it had something to do with fullscreen behaviors) and whether its viable to change it without regressing other behaviors.

I'll leave the burden of that research onto you or others.

[Lozgemk]

Thanks for the answer. Would it be possible to have an option in the settings to control this, so we don't lose anything for people who like the current behavior?

[twilwa]

+1 on this (sorry, couldn't find the emoji.) My primary issue being that it's inconsistent behavior across my terminal applications, ghostty is my main workspace/daily driver & the only one who behaves this way, so the added ergonomic friction impacts me pretty significantly.