This is a minor, but very annoying bug that makes hyprctl commands not execute after hyprlock.
For all I know, this could be intentional behavior, but if it is, is there an alternative for what I’m trying to achieve?
This is my startup config:
exec-once = [workspace $specialWorkspace silent] xdg-terminal-exec ncmpcpp && sleep 1 && hyprctl dispatch movetoworkspacesilent special:special, title:ncmpcpp
exec-once = hyprlock
The first [workspace] thing is not needed here as it doesn’t do much since xdg-terminal-exec doesn’t work with it, I kept it just to show I tried that.
To get to the point, this just straight up doesn’t work.
The terminal launches on the workspace I am currently on, and never gets moved to special due to hyprlock starting.
I could use a window rule for ncmpcpp, but that makes any ncmpcpp I open start on the special workspace, that’s not what I want to do.
Hyprland version
hyprctl version
Hyprland 0.54.0 built from branch main at commit 2fde538e0fa5663ac99f631fcfee6742e09368f6 clean (algo/scrolling: improve behavior with focus_fit_method = center ( 13795)).
Date: Thu Mar 26 21:38:56 2026
Tag: v0.54.0-129-g2fde538e0, commits: 7064
Libraries:
Hyprgraphics: built against 0.5.0, system has 0.5.0
Hyprutils: built against 0.11.1, system has 0.11.1
Hyprcursor: built against 0.1.13, system has 0.1.13
Hyprlang: built against 0.6.8, system has 0.6.8
Aquamarine: built against 0.10.0, system has 0.10.0
Version ABI string: 2fde538e0fa5663ac99f631fcfee6742e09368f6_aq_0.10_hu_0.11_hg_0.5_hc_0.1_hlg_0.6
no flags were set