.shell powershell
# Reload whkd configuration
# alt + o : taskkill /f /im whkd.exe && start /b whkd # if shell is cmd
alt + o : taskkill /f /im whkd.exe; Start-Process whkd -WindowStyle hidden # if shell is pwsh / powershell
alt + shift + o : komorebic reload-configuration
# App shortcuts - these require shell to be pwsh / powershell
# The apps will be focused if open, or launched if not open
#win + f : if ($wshell.AppActivate('Firefox') -eq $False) { start firefox }
win + shift + q : komorebic close
#alt + m : komorebic minimize
# Focus windows
win + left : komorebic focus left
win + down : komorebic focus down
win + up : komorebic focus up
win + right : komorebic focus right
#alt + shift + oem_4 : komorebic cycle-focus previous # oem_4 is [
#alt + shift + oem_6 : komorebic cycle-focus next # oem_6 is ]
# Move windows
win + shift + left : komorebic move left
win + shift + down : komorebic move down
win + shift + up : komorebic move up
win + shift + right : komorebic move right
win + shift + return : komorebic promote
# Stack windows
#alt + left : komorebic stack left
#alt + down : komorebic stack down
#alt + up : komorebic stack up
#alt + right : komorebic stack right
#alt + oem_1 : komorebic unstack # oem_1 is ;
#alt + oem_4 : komorebic cycle-stack previous # oem_4 is [
#alt + oem_6 : komorebic cycle-stack next # oem_6 is ]
# Resize
win + alt + right : komorebic resize-axis horizontal increase
win + alt + left : komorebic resize-axis horizontal decrease
win + alt + down : komorebic resize-axis vertical increase
win + alt + up : komorebic resize-axis vertical decrease
# Manipulate windows
win + t : komorebic toggle-float
win + ctrl + t : komorebic toggle-workspace-layer
win + f : komorebic toggle-monocle
# Window manager options
win + shift + r : komorebic retile
win + alt + p : komorebic toggle-pause
# Layouts
win + x : komorebic flip-layout horizontal
win + c : komorebic flip-layout vertical
# Workspaces
win + 1 : komorebic focus-workspace 0
win + 2 : komorebic focus-workspace 1
win + 3 : komorebic focus-workspace 2
win + 4 : komorebic focus-workspace 3
win + 5 : komorebic focus-workspace 4
win + 6 : komorebic focus-workspace 5
win + 7 : komorebic focus-workspace 6
win + 8 : komorebic focus-workspace 7
# Move windows across workspaces
win + shift + 1 : komorebic move-to-workspace 0
win + shift + 2 : komorebic move-to-workspace 1
win + shift + 3 : komorebic move-to-workspace 2
win + shift + 4 : komorebic move-to-workspace 3
win + shift + 5 : komorebic move-to-workspace 4
win + shift + 6 : komorebic move-to-workspace 5
win + shift + 7 : komorebic move-to-workspace 6
win + shift + 8 : komorebic move-to-workspace 7
# apps
win + shift + s : explorer ms-screenclip://capture
win + e : C:\Windows\explorer.exe
Output of komorebic check
KOMOREBI_CONFIG_HOME detected: D:\Lelou\custom-desktop\config\komorebi
Looking for configuration files in D:\Lelou\custom-desktop\config\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
Found D:\Lelou\custom-desktop\config\whkd\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
Originally created by @LelouBil on GitHub (Mar 27, 2025).
### Summary
I have two monitors, and I enabled transparency for unfocused windows.
I am using masir to make the focus follow my mouse.
If I enable monocle mode on my primary monitor, the window is focused and fully opaque.
When I drag my mouse to my second monitor, the window become unfocused and transparent because of masir.
When I drag my mouse back on my primary monitor, the window becomse **focused but still transparent**
When I use keybinds to switch focus everything works fine.
I tested it with Firefox being the application that was stuck transarent
### Version Information
OS name: Microsoft Windows 11 Professionnel
OS version: 10.0.26100 N/A build 26100
komorebic 0.1.35
tag:v0.1.35
commit_hash:992bc2ab
build_time:2025-03-22 17:41:57 +00:00
build_env:rustc 1.85.1 (4eb161250 2025-03-15),stable-x86_64-pc-windows-msvc
### Komorebi Configuration
```json
{
"$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/v0.1.35/schema.json",
"animation": {
"enabled": true,
"fps": 165,
"style": "EaseInOutQuart"
},
"transparency": true,
"transparency_alpha": 225,
"app_specific_configuration_path": "applications.json",
"window_hiding_behaviour": "Cloak",
"cross_monitor_move_behaviour": "Insert",
"default_workspace_padding": 10,
"default_container_padding": 0,
"border": false,
"border_width": 6,
"border_offset": -1,
"theme": {
"palette": "Base16",
"name": "Ashes",
"unfocused_border": "Base03",
"bar_accent": "Base0D"
},
"stackbar": {
"height": 40,
"mode": "OnStack",
"tabs": {
"width": 300
}
},
"monitors": [
{
"container_padding": 0,
"workspace_padding": 2,
"work_area_offset": {
"top": 0,
"left": 0,
"right": 0,
"bottom": 0
},
"workspaces": [
{
"name": "I",
"layout": "BSP"
},
{
"name": "II",
"layout": "BSP"
},
{
"name": "III",
"layout": "BSP"
},
{
"name": "IV",
"layout": "BSP"
},
{
"name": "V",
"layout": "BSP"
},
{
"name": "VI",
"layout": "BSP"
},
{
"name": "VII",
"layout": "BSP"
},
{
"name": "special",
"layout": "HorizontalStack"
}
]
},
{
"work_area_offset": {
"top": 0,
"left": 0,
"right": 0,
"bottom": 0
},
"workspaces": [
{
"name": "I",
"layout": "RightMainVerticalStack"
}
]
}
]
}
```
### Hotkey Configuration
```
.shell powershell
# Reload whkd configuration
# alt + o : taskkill /f /im whkd.exe && start /b whkd # if shell is cmd
alt + o : taskkill /f /im whkd.exe; Start-Process whkd -WindowStyle hidden # if shell is pwsh / powershell
alt + shift + o : komorebic reload-configuration
# App shortcuts - these require shell to be pwsh / powershell
# The apps will be focused if open, or launched if not open
#win + f : if ($wshell.AppActivate('Firefox') -eq $False) { start firefox }
win + shift + q : komorebic close
#alt + m : komorebic minimize
# Focus windows
win + left : komorebic focus left
win + down : komorebic focus down
win + up : komorebic focus up
win + right : komorebic focus right
#alt + shift + oem_4 : komorebic cycle-focus previous # oem_4 is [
#alt + shift + oem_6 : komorebic cycle-focus next # oem_6 is ]
# Move windows
win + shift + left : komorebic move left
win + shift + down : komorebic move down
win + shift + up : komorebic move up
win + shift + right : komorebic move right
win + shift + return : komorebic promote
# Stack windows
#alt + left : komorebic stack left
#alt + down : komorebic stack down
#alt + up : komorebic stack up
#alt + right : komorebic stack right
#alt + oem_1 : komorebic unstack # oem_1 is ;
#alt + oem_4 : komorebic cycle-stack previous # oem_4 is [
#alt + oem_6 : komorebic cycle-stack next # oem_6 is ]
# Resize
win + alt + right : komorebic resize-axis horizontal increase
win + alt + left : komorebic resize-axis horizontal decrease
win + alt + down : komorebic resize-axis vertical increase
win + alt + up : komorebic resize-axis vertical decrease
# Manipulate windows
win + t : komorebic toggle-float
win + ctrl + t : komorebic toggle-workspace-layer
win + f : komorebic toggle-monocle
# Window manager options
win + shift + r : komorebic retile
win + alt + p : komorebic toggle-pause
# Layouts
win + x : komorebic flip-layout horizontal
win + c : komorebic flip-layout vertical
# Workspaces
win + 1 : komorebic focus-workspace 0
win + 2 : komorebic focus-workspace 1
win + 3 : komorebic focus-workspace 2
win + 4 : komorebic focus-workspace 3
win + 5 : komorebic focus-workspace 4
win + 6 : komorebic focus-workspace 5
win + 7 : komorebic focus-workspace 6
win + 8 : komorebic focus-workspace 7
# Move windows across workspaces
win + shift + 1 : komorebic move-to-workspace 0
win + shift + 2 : komorebic move-to-workspace 1
win + shift + 3 : komorebic move-to-workspace 2
win + shift + 4 : komorebic move-to-workspace 3
win + shift + 5 : komorebic move-to-workspace 4
win + shift + 6 : komorebic move-to-workspace 5
win + shift + 7 : komorebic move-to-workspace 6
win + shift + 8 : komorebic move-to-workspace 7
# apps
win + shift + s : explorer ms-screenclip://capture
win + e : C:\Windows\explorer.exe
```
### Output of komorebic check
```
KOMOREBI_CONFIG_HOME detected: D:\Lelou\custom-desktop\config\komorebi
Looking for configuration files in D:\Lelou\custom-desktop\config\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
Found D:\Lelou\custom-desktop\config\whkd\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
```
If this is only happening when using masir then this might be a bug in how masir handles multi window applications 🤔
@LGUG2Z commented on GitHub (Mar 27, 2025):
If this is only happening when using `masir` then this might be a bug in how `masir` handles multi window applications 🤔
I am not sure if the problem is with masir or komorebi, but what made me file the issue for komorebi is the fact that the window is focused when hovering the mouse so it seems that masir is doing its job correctly. It's just that the window is still transparent
@LelouBil commented on GitHub (Mar 27, 2025):
I am not sure if the problem is with masir or komorebi, but what made me file the issue for komorebi is the fact that *the window is focused when hovering the mouse* so it seems that masir is doing its job correctly. It's just that the window is still transparent
Can confirm, have experienced a similar issue when focusing monocle'd windows with the mouse. They do focus, but stay transparent as if they aren't. Not using masir btw so it's most likely a komorebi issue. Windows focus fine if focused via hotkey.
@Surnyy commented on GitHub (Apr 3, 2025):
Can confirm, have experienced a similar issue when focusing monocle'd windows with the mouse. They do focus, but stay transparent as if they aren't. Not using masir btw so it's most likely a komorebi issue. Windows focus fine if focused via hotkey.
Next steps would be to keep komorebi running in the foreground (or tail the logs) and share the relevant logs from whenever you see this issue reproduced in the absence of any reproducible repro steps
@LGUG2Z commented on GitHub (Apr 4, 2025):
Next steps would be to keep komorebi running in the foreground (or tail the logs) and share the relevant logs from whenever you see this issue reproduced in the absence of any reproducible repro steps
I just did it, there are no logs added when focusing a monocle mode window using the mouse, it's like komorebi doesn't know about the focus change at all.
Here are the logs added when focusing a monocle mode window with the mouse :
2025-04-03T22:32:31.081315Z INFO process_event{event="FocusChange" winevent="SystemForeground" hwnd=199248}:update_focused_workspace{follow_focus=true trigger_focus=false}: komorebi::window_manager: updating
2025-04-03T22:32:31.081726Z INFO process_event{event="FocusChange" winevent="SystemForeground" hwnd=199248}:focus_window{idx=0}: komorebi::container: focusing window
2025-04-03T22:32:31.081863Z INFO process_event{event="FocusChange" winevent="SystemForeground" hwnd=199248}:focus_container{idx=0}: komorebi::workspace: focusing container
2025-04-03T22:32:31.082449Z INFO process_event{event="FocusChange" winevent="SystemForeground" hwnd=199248}: komorebi::process_event: processed: (hwnd: 199248, title: PowerShell, exe: WindowsTerminal.exe, class: CASCADIA_HOSTING_WINDOW_CLASS)
And here are logs when focusing a monocle mode window with keybindings/komorebic :
2025-04-03T22:35:42.678157Z INFO process_command{FocusWindow(Left)}:focus_container_in_direction{direction=Left}: komorebi::window_manager: focusing container
2025-04-03T22:35:42.678277Z INFO process_command{FocusWindow(Left)}:focus_container_in_direction{direction=Left}:focus_monitor{idx=0}: komorebi::window_manager: focusing monitor
2025-04-03T22:35:42.681924Z INFO process_command{FocusWindow(Left)}: komorebi::process_command: processed
@LelouBil commented on GitHub (Apr 4, 2025):
I just did it, there are no logs added when focusing a monocle mode window using the mouse, it's like komorebi doesn't know about the focus change at all.
Here are the logs added when focusing a monocle mode window with the mouse :
```
2025-04-03T22:32:31.081315Z INFO process_event{event="FocusChange" winevent="SystemForeground" hwnd=199248}:update_focused_workspace{follow_focus=true trigger_focus=false}: komorebi::window_manager: updating
2025-04-03T22:32:31.081726Z INFO process_event{event="FocusChange" winevent="SystemForeground" hwnd=199248}:focus_window{idx=0}: komorebi::container: focusing window
2025-04-03T22:32:31.081863Z INFO process_event{event="FocusChange" winevent="SystemForeground" hwnd=199248}:focus_container{idx=0}: komorebi::workspace: focusing container
2025-04-03T22:32:31.082449Z INFO process_event{event="FocusChange" winevent="SystemForeground" hwnd=199248}: komorebi::process_event: processed: (hwnd: 199248, title: PowerShell, exe: WindowsTerminal.exe, class: CASCADIA_HOSTING_WINDOW_CLASS)
```
And here are logs when focusing a *monocle mode* window with *keybindings/komorebic* :
```
2025-04-03T22:35:42.678157Z INFO process_command{FocusWindow(Left)}:focus_container_in_direction{direction=Left}: komorebi::window_manager: focusing container
2025-04-03T22:35:42.678277Z INFO process_command{FocusWindow(Left)}:focus_container_in_direction{direction=Left}:focus_monitor{idx=0}: komorebi::window_manager: focusing monitor
2025-04-03T22:35:42.681924Z INFO process_command{FocusWindow(Left)}: komorebi::process_command: processed
```
I don't see this as something I'll be looking at actively, mainly because I can't reproduce it independently, and also because transparency is not really a Tier 1 feature (i.e. you can just turn it off and you still have full tiling window manager functionality) - but I can help guide an investigation in this thread by anyone who wants to dig deeper, add their own trace logs etc.
@LGUG2Z commented on GitHub (Apr 4, 2025):
I don't see this as something I'll be looking at actively, mainly because I can't reproduce it independently, and also because transparency is not really a Tier 1 feature (i.e. you can just turn it off and you still have full tiling window manager functionality) - but I can help guide an investigation in this thread by anyone who wants to dig deeper, add their own trace logs etc.
I am also having this issue, happens on any program. I have had this with and without using masir, so it's definitely not that. Unless just having it installed messes with it, as I have had it installed ever since I started using komorebi. I suppose I am using Cairo Desktop, though I'm not sure if that would affect anything here. Could this be related to having multiple monitors?
@Tharpadarp commented on GitHub (Jul 21, 2025):
I am also having this issue, happens on any program. I have had this with and without using masir, so it's definitely not that. Unless just having it installed messes with it, as I have had it installed ever since I started using komorebi. I suppose I am using Cairo Desktop, though I'm not sure if that would affect anything here. Could this be related to having multiple monitors?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @LelouBil on GitHub (Mar 27, 2025).
Summary
I have two monitors, and I enabled transparency for unfocused windows.
I am using masir to make the focus follow my mouse.
If I enable monocle mode on my primary monitor, the window is focused and fully opaque.
When I drag my mouse to my second monitor, the window become unfocused and transparent because of masir.
When I drag my mouse back on my primary monitor, the window becomse focused but still transparent
When I use keybinds to switch focus everything works fine.
I tested it with Firefox being the application that was stuck transarent
Version Information
OS name: Microsoft Windows 11 Professionnel
OS version: 10.0.26100 N/A build 26100
komorebic 0.1.35
tag:v0.1.35
commit_hash:992bc2ab
build_time:2025-03-22 17:41:57 +00:00
build_env:rustc 1.85.1 (4eb161250 2025-03-15),stable-x86_64-pc-windows-msvc
Komorebi Configuration
Hotkey Configuration
Output of komorebic check
@LGUG2Z commented on GitHub (Mar 27, 2025):
If this is only happening when using
masirthen this might be a bug in howmasirhandles multi window applications 🤔@LelouBil commented on GitHub (Mar 27, 2025):
I am not sure if the problem is with masir or komorebi, but what made me file the issue for komorebi is the fact that the window is focused when hovering the mouse so it seems that masir is doing its job correctly. It's just that the window is still transparent
@Surnyy commented on GitHub (Apr 3, 2025):
Can confirm, have experienced a similar issue when focusing monocle'd windows with the mouse. They do focus, but stay transparent as if they aren't. Not using masir btw so it's most likely a komorebi issue. Windows focus fine if focused via hotkey.
@LGUG2Z commented on GitHub (Apr 4, 2025):
Next steps would be to keep komorebi running in the foreground (or tail the logs) and share the relevant logs from whenever you see this issue reproduced in the absence of any reproducible repro steps
@LelouBil commented on GitHub (Apr 4, 2025):
I just did it, there are no logs added when focusing a monocle mode window using the mouse, it's like komorebi doesn't know about the focus change at all.
Here are the logs added when focusing a monocle mode window with the mouse :
And here are logs when focusing a monocle mode window with keybindings/komorebic :
@LGUG2Z commented on GitHub (Apr 4, 2025):
I don't see this as something I'll be looking at actively, mainly because I can't reproduce it independently, and also because transparency is not really a Tier 1 feature (i.e. you can just turn it off and you still have full tiling window manager functionality) - but I can help guide an investigation in this thread by anyone who wants to dig deeper, add their own trace logs etc.
@Tharpadarp commented on GitHub (Jul 21, 2025):
I am also having this issue, happens on any program. I have had this with and without using masir, so it's definitely not that. Unless just having it installed messes with it, as I have had it installed ever since I started using komorebi. I suppose I am using Cairo Desktop, though I'm not sure if that would affect anything here. Could this be related to having multiple monitors?