Pre-submit Checks

• I have searched Warp bugs and there are no duplicates
• I have searched Warp known issues page and my issue is not there
• I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix).
• I have technical issue and have included the logs (optional, but helps expedite the bug fix).

Describe the bug

When the Dedicated Hotkey Window is focused on a secondary (non-primary) display and I press Cmd+N to open a new window, the new window is created but appears on the primary display instead of the current one, and it is not activated/brought to focus. Since my attention is on the secondary display, it looks like Cmd+N did nothing at all — I have to manually switch to the primary display/Space to find the new window sitting there unfocused.

For comparison, Ghostty handles this correctly: opening a new window while focused on a window on a secondary display creates the new window and immediately activates it in place (on the current screen), which is much more intuitive and avoids this "did nothing happen?" confusion.

To reproduce

Steps to reproduce:

1. Enable "Dedicated Hotkey Window" in Warp Settings.
2. Use two displays with "Displays have separate Spaces" enabled in macOS (Mission Control settings).
3. Trigger the Warp global hotkey while focused on the secondary (non-primary) display, so the Dedicated Hotkey Window opens there.
4. With the Dedicated Hotkey Window focused on the secondary display, press Cmd+N.
5. Observe: nothing visibly happens on the secondary display.
6. Switch to the primary display (or check Mission Control) — a new regular Warp window has been created there, but it was never brought to front or given keyboard focus.

Expected behavior

The new window created via Cmd+N should open on the same screen/Space as the currently focused window (or at minimum be automatically activated/brought to front wherever it opens), matching Ghostty's behavior.

Screenshots, videos, and logs

No response

Operating system (OS)

macOS

Operating system and version

macOS 26.5 (Build 25F71)

Shell Version

zsh 5.9 (arm64-apple-darwin25.0)

Current Warp version

v0.2026.07.01.09.21.01

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

Two displays, separate Spaces enabled. Primary/main display is an external 5120x2880 monitor; secondary is the built-in MacBook Retina display (3024x1964). This setup (external monitor set as primary, built-in as secondary) is similar to the configuration described in #13273, which may share a related root cause around how the Dedicated Hotkey Window / new-window placement logic determines the "current"/"active" screen on multi-monitor setups — though the trigger differs (fullscreen-app hotkey invocation vs. Cmd+N pressed from within the already-open dedicated window).

Does this block you from using Warp daily?

No

Is this an issue only in Warp?

Yes, I confirmed that this only happens in Warp, not other terminals.