Dispatch exec with +tag to open browser windows results in tags being appyied to all new windows from this action on

Bugs / FRs / Support
, ,
1
Hyprland version 
Hyprland 0.53.3 built from branch v0.53.3 at commit dd220efe7b1e292415bd0ea7161f63df9c95bfd3 clean (version: bump to 0.53.3).
Date: Sat Jan 24 20:02:06 2026
Tag: v0.53.3, commits: 6793

Libraries:
Hyprgraphics: built against 0.5.0, system has 0.5.0
Hyprutils: built against 0.11.0, system has 0.11.0
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: dd220efe7b1e292415bd0ea7161f63df9c95bfd3_aq_0.10_hu_0.11_hg_0.5_hc_0.1_hlg_0.6
no flags were set

Hi,

There’s this strange bug that causes a dispatch exec command with +tag to apply the defined tag for all new windows from this action on, if the exec command is related to a browser.

Steps to reproduce:

  1. Open a terminal and run hyprctl dispatch exec “[tag +test] zen-browser” and hyprctl dispatch exec “[tag +test2] helium-browser”.
  2. Wait for the browser windows to open, then open a new terminal window and run hyprctl clients -j. You’ll notice that the new terminal window will have the tags test and test2.
  3. Now, do hyprctl hyprctl dispatch exec "[tag +test3] alacritty".
  4. After the windows open, open a new terminal window and run hyprctl clients -j. You’ll notice that the new terminal window will not have the tag test3.
2

Looks fun! I know what i’m playing around with tonight!

1 Like