Kitty notification focus issue

[ajatkj]

I'm running a Kitty session using kitty --session sessions/session1.conf, which opens multiple windows and tabs.

The issue is that when a notification comes from one of these windows, clicking on it takes me back to the window where I originally launched the Kitty session, rather than the window that actually triggered the notification.

Is there any way to make clicking a notification focus the window it originated from? Going back to the window that launched the session isn't helpful.

[g4lb]

Kitty focuses the source window for its own notifications.
Yours likely come from another tool. To test, run printf '\x1b]99;;hi\x1b\\', change focus, then click.

[ajatkj]

Same issue with this test as well.
Steps:

1. I open a new kitty window (window 1)
2. I run kitty which opens another kitty instance (window 2)
3. From window 2 I ran printf '\x1b]99;;hi\x1b\\', changed focus to another application, clicked on notification I am taken to window 1 but I notice for a brief second I can see window 2 before window 1 is activated.

I am on MacOS Golden Gate 27.0.1 (26A434) if that helps. Not using any external window manager.

[g4lb]

Two instances may be the cause: macOS may activate the first. Try kitty --single-instance for both.

[ajatkj]

I tried kitty --single-instance as suggested, but unfortunately the behavior is exactly the same.

Clicking the notification still takes me to the first Kitty window (the one from which I launched the command), rather than the window that generated the notification.

I'll put together a minimal reproducer and open an issue as requested.

[kovidgoyal]

That depends on your window manager and if whatever is generating the notifications is using kitty's notification protocol or not.

[ajatkj]

I am on MacOS Golden Gate 27.0.1 (26A434). Forgot to mention earlier.

I ran the test suggested here which is basic printf but its the same issue.

[kovidgoyal]

PLease provide a proper reproducer. Your original post talked about a session file which implies a single kityt instance, now you are talking about two kitty instances. Open an issue, fill in all the information asked for in the issue template and provide a minimal set of steps to reproduce your issue.

[kovidgoyal]

On Wed, Nov 04, 2026 at 06:24:24AM -0800, Ankit wrote: I tried `kitty --single-instance` as suggested, but unfortunately the behavior is exactly the same.

That's not how --single-instance works, you need to run kitty using --single-instance twice. then the windows from those two invocations will belong to a single process. Or just use cmd+N to create a new kitty window.