Originally created by @itsleemcguire on GitHub (Jul 15, 2025).
Summary
I have enabled the windows setting Accessibility -mouse- activate on hover and komorebi seems to be disabling it after a boot.
I have disabled komorebi on boot, Windows boots and keeps the Activate on Hover setting enabled.
With komorebi auto-launching on boot, Or when i then run komorebi from Terminal the accessibility setting gets turned off and interestingly the "amount of time mouse needs to be over a window to activate it" slider gets reset, which it doesnt do when you disable and reenable the "activate on hover" setting manually. It seems theres a big bug resetting some of windows accessibility settings somehow
Version Information
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.26100 N/A Build 26100
komorebic 0.1.37
tag:v0.1.37
commit_hash:00384ce3
build_time:2025-05-17 19:16:53 +00:00
build_env:rustc 1.87.0 (17067e9ac 2025-05-09),stable-x86_64-pc-windows-msvc
i dont know what this is so i assume its just the default as i havent touched it
Output of komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\itsle
Looking for configuration files in C:\Users\itsle
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\itsle.config\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 @itsleemcguire on GitHub (Jul 15, 2025).
### Summary
I have enabled the windows setting Accessibility -mouse- activate on hover and komorebi seems to be disabling it after a boot.
I have disabled komorebi on boot, Windows boots and keeps the Activate on Hover setting enabled.
With komorebi auto-launching on boot, Or when i then run komorebi from Terminal the accessibility setting gets turned off and interestingly the "amount of time mouse needs to be over a window to activate it" slider gets reset, which it doesnt do when you disable and reenable the "activate on hover" setting manually. It seems theres a big bug resetting some of windows accessibility settings somehow
### Version Information
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.26100 N/A Build 26100
komorebic 0.1.37
tag:v0.1.37
commit_hash:00384ce3
build_time:2025-05-17 19:16:53 +00:00
build_env:rustc 1.87.0 (17067e9ac 2025-05-09),stable-x86_64-pc-windows-msvc
### Komorebi Configuration
```json
{
"$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/v0.1.37/schema.json",
"app_specific_configuration_path": "$Env:USERPROFILE/applications.json",
"window_hiding_behaviour": "Cloak",
"cross_monitor_move_behaviour": "Insert",
"default_workspace_padding": 5,
"default_container_padding": 5,
"border": true,
"border_width": 8,
"mouse_follows_focus": false,
"border_offset": -1,
"border_colours": {
"single": "#FC6A03",
"stack": "#00a542",
"monocle": "#ff3399",
"unfocused": "#808080"
},
"monitors": [
{
"workspaces": [
{
"name": "I",
"layout": "BSP"
},
{
"name": "II",
"layout": "VerticalStack"
},
{
"name": "III",
"layout": "HorizontalStack"
},
{
"name": "IV",
"layout": "UltrawideVerticalStack"
},
{
"name": "V",
"layout": "Rows"
},
{
"name": "VI",
"layout": "Grid"
},
{
"name": "VII",
"layout": "RightMainVerticalStack"
}
]
}
]
}
```
### Hotkey Configuration
i dont know what this is so i assume its just the default as i havent touched it
### Output of komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\itsle
Looking for configuration files in C:\Users\itsle
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\itsle\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
adam
added the bug label 2026-01-05 14:52:11 +01:00
@LGUG2Z commented on GitHub (Jul 15, 2025):
You'll have to compile your own version of komorebi which removes this cleanup hook:
https://github.com/LGUG2Z/komorebi/blob/master/komorebi/src/main.rs#L364-L366
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 @itsleemcguire on GitHub (Jul 15, 2025).
Summary
I have enabled the windows setting Accessibility -mouse- activate on hover and komorebi seems to be disabling it after a boot.
I have disabled komorebi on boot, Windows boots and keeps the Activate on Hover setting enabled.
With komorebi auto-launching on boot, Or when i then run komorebi from Terminal the accessibility setting gets turned off and interestingly the "amount of time mouse needs to be over a window to activate it" slider gets reset, which it doesnt do when you disable and reenable the "activate on hover" setting manually. It seems theres a big bug resetting some of windows accessibility settings somehow
Version Information
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.26100 N/A Build 26100
komorebic 0.1.37
tag:v0.1.37
commit_hash:00384ce3
build_time:2025-05-17 19:16:53 +00:00
build_env:rustc 1.87.0 (17067e9ac 2025-05-09),stable-x86_64-pc-windows-msvc
Komorebi Configuration
Hotkey Configuration
i dont know what this is so i assume its just the default as i havent touched it
Output of komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\itsle
Looking for configuration files in C:\Users\itsle
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\itsle.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
@LGUG2Z commented on GitHub (Jul 15, 2025):
You'll have to compile your own version of komorebi which removes this cleanup hook:
https://github.com/LGUG2Z/komorebi/blob/master/komorebi/src/main.rs#L364-L366
@LGUG2Z commented on GitHub (Jul 15, 2025):
Someone can add a config option to conditionally disable this if they want an easy PR to contribute