THe app in alt+tab is ok. It is the artifact it leaves on my screen that drives me nuts.
I try to put the task on a not so much used desktop. 
Since this week, with the espanso from nixos-unstable on KDE Plasma 6.1 I donât get the extra app anymore!
I have tried but I canât get this to work on waylandâŚ
Tried enabling the options services.espanso.wayland = true, services.espanso.package = pkgs.espanso-wayland and services.espanso.enable = true. And also added espanso-wayland to the environment.systemPackages, nothing worked.
This is the log from espanso log:
$ espanso log
23:44:06 [daemon(449587)] [INFO] reading configs from: "/home/abdulla/.config/espanso"
23:44:06 [daemon(449587)] [INFO] reading packages from: "/home/abdulla/.config/espanso/match/packages"
23:44:06 [daemon(449587)] [INFO] using runtime dir: "/home/abdulla/.cache/espanso"
23:44:06 [daemon(449587)] [INFO] system info: NixOS v24.11 - kernel: 6.6.41
23:44:06 [daemon(449587)] [WARN] keyboard layout watcher couldn't determine active layout.
23:44:06 [daemon(449587)] [INFO] espanso version: 2.2.1
23:44:06 [daemon(449587)] [INFO] spawning the worker process...
23:44:06 [daemon(449587)] [INFO] watching for changes in path: "/home/abdulla/.config/espanso"
23:44:06 [daemon(449587)] [INFO] binded to IPC unix socket: /home/abdulla/.cache/espanso/espansodaemonv2.sock
23:44:06 [worker(449593)] [INFO] reading configs from: "/home/abdulla/.config/espanso"
23:44:06 [worker(449593)] [INFO] reading packages from: "/home/abdulla/.config/espanso/match/packages"
23:44:06 [worker(449593)] [INFO] using runtime dir: "/home/abdulla/.cache/espanso"
23:44:06 [worker(449593)] [INFO] system info: NixOS v24.11 - kernel: 6.6.41
23:44:06 [worker(449593)] [INFO] binded to IPC unix socket: /home/abdulla/.cache/espanso/espansoworkerv2.sock
23:44:06 [worker(449593)] [INFO] using WaylandAppInfoProvider
23:44:06 [worker(449593)] [WARN] EVDEV backend is being used, but without enabling linux capabilities.
23:44:06 [worker(449593)] [WARN] Although you CAN run espanso EVDEV backend as root, it's not recommended due
23:44:06 [worker(449593)] [WARN] to security reasons. Espanso supports linux capabilities to limit the attack surface
23:44:06 [worker(449593)] [WARN] area by only leveraging on the CAP_DAC_OVERRIDE capability (needed to work with
23:44:06 [worker(449593)] [INFO] monitoring the status of the daemon process
23:44:06 [worker(449593)] [WARN] /dev/input/* devices to detect and inject text) and disabling it as soon as the
23:44:06 [worker(449593)] [WARN] initial setup is completed.
23:44:06 [worker(449593)] [INFO] detection module will use this keyboard layout: [R=evdev, M=pc105, L=us, V=, O=]
23:44:06 [worker(449593)] [INFO] using EVDEVSource
23:44:06 [worker(449593)] [ERROR] Unable to open EVDEV devices, this usually has to do with permissions.
23:44:06 [worker(449593)] [ERROR] You can either add the current user to the 'input' group or run espanso as root
23:44:06 [worker(449593)] [ERROR] thread 'engine thread' panicked at 'failed to initialize detector module: detection source initialization failed': espanso/src/cli/worker/engine/mod.rs:141
23:44:06 [worker(449593)] [ERROR] Unable to block the LinuxEventLoop: receiving on an empty and disconnected channel
23:44:06 [worker(449593)] [ERROR] thread 'main' panicked at 'unable to run main eventloop: receiving on an empty and disconnected channel': espanso/src/cli/worker/mod.rs:160
23:44:06 [daemon(449587)] [ERROR] received unexpected exit code from worker 101, exiting
Does a espanso stop; espanso start --unmanaged work? Thatâs what I do when I get any issueâŚ
sadly it didnât 
I had removed espanso for the time being and will try again later someday~