KDE Wayland: notification action points to virtual desktop with no Codex window

What version of the Codex App are you using (From “About Codex” dialog)?

codex-cli 0.146.0, reported by codex --version after the occurrence. This is
the CLI-reported version; the About-dialog build number was not captured.

What subscription do you have?

Pro 5x.

What platform is your computer?

Linux 7.1.3-ogc3.4.fc44.x86_64 x86_64 unknown

Bazzite 44.20260713.0 (Kinoite), KDE Plasma/KWin 6.7.2, Wayland.

What issue are you seeing?

Codex action notifications intermittently point to the wrong KDE virtual
desktop.

In the captured example, a Codex notification said a thread was waiting for
input and offered the action Jump to Desktop 1. Desktop 1 had no Codex
instances or windows running on it. Using the action therefore navigated away
from the actual Codex window instead of bringing the originating thread into
view.

This report concerns the incorrect action target, not merely which desktop
displays the notification.

What steps can reproduce the bug?

1. Run Codex with its windows/instances on KDE virtual desktops other than

Desktop 1.

1. Let a background Codex turn reach a permission or question state that emits

a “waiting on you” action notification.

1. Inspect the notification's desktop action.
2. At least some of the time, it says Jump to Desktop 1 even though no Codex

window is on Desktop 1.

1. Activate the action; KDE switches to the empty/wrong desktop rather than the

window/thread that generated the notification.

The behavior is intermittent; the reporter has not isolated a deterministic
sequence beyond notifications being emitted while Codex is running on other
virtual desktops.

What is the expected behavior?

The notification action should activate the Codex window/thread that generated
the notification, switching to the virtual desktop where that window actually
resides. If Codex or the desktop shell cannot identify the originating window,
the notification should not offer a misleading desktop target.

Additional information

A screenshot captured on 2026-07-30 shows the Codex notification and its
Jump to Desktop 1 action while Desktop 1 contained no Codex instance.

The closest searched issues were #27436 (chat-scoped notification suppression)
and #26801 (CLI Freedesktop notification delivery); neither covers an action
targeting a virtual desktop with no Codex window.