[BUG]: autostarted komorebi does not respect app specific configuration #382

New Issue

2026-01-05T14:50:13+01:00

adam commented

2026-01-05 14:50:13 +01:00

Originally created by @PatrikTrefil on GitHub (May 20, 2024).

Describe the bug
I am going to use PowerToys as an example, but it happens for other programs too. When komorebi is started automatically (setup using komorebic enable-autostart) and PowerToys is started automatically (setup using PowerToys configuration GUI), PowerToys Run keeps getting tiled or does not display at all, eventhough it is configured not to be tiled using the default applications.yaml file. If I restart komorebi using komorebic stop and komorebic start, everything starts working.

To Reproduce
Steps to reproduce the behavior:

komorebic enable-autostart
Autostart PowerToys
Restart PC

Expected behavior
As soon as both komorebi and PowerToys are started I can use PowerToys Run without the window getting tiled.

Screenshots and Videos

Operating System

OS Name:                   Microsoft Windows 11 Home
OS Version:                10.0.22631 N/A Build 22631

komorebic check Output

KOMOREBI_CONFIG_HOME detected: C:\Users\patri\.config\komorebi

Looking for configuration files in C:\Users\patri\.config\komorebi

Found komorebi.json; this file can be passed to the start command with the --config flag

Found C:\Users\patri\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag

Additional context
Restarting the problematic application (e.g. PowerToys) does not help. The only way to repair it is to restart komorebi manually.

I am also using yasb and whkd.

Originally created by @PatrikTrefil on GitHub (May 20, 2024). **Describe the bug** I am going to use PowerToys as an example, but it happens for other programs too. When komorebi is started automatically (setup using `komorebic enable-autostart`) and PowerToys is started automatically (setup using PowerToys configuration GUI), PowerToys Run keeps getting tiled or does not display at all, eventhough it is configured not to be tiled using the default `applications.yaml` file. If I restart komorebi using `komorebic stop` and `komorebic start`, everything starts working. **To Reproduce** Steps to reproduce the behavior: 1. `komorebic enable-autostart` 2. Autostart PowerToys 3. Restart PC **Expected behavior** As soon as both komorebi and PowerToys are started I can use PowerToys Run without the window getting tiled. **Screenshots and Videos** ![image](https://github.com/LGUG2Z/komorebi/assets/36563492/71d2aec6-fe33-4c81-8084-0d850399835d) **Operating System** ``` OS Name: Microsoft Windows 11 Home OS Version: 10.0.22631 N/A Build 22631 ``` **`komorebic check` Output** ``` KOMOREBI_CONFIG_HOME detected: C:\Users\patri\.config\komorebi Looking for configuration files in C:\Users\patri\.config\komorebi Found komorebi.json; this file can be passed to the start command with the --config flag Found C:\Users\patri\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag ``` **Additional context** Restarting the problematic application (e.g. PowerToys) does not help. The only way to repair it is to restart komorebi manually. I am also using yasb and whkd.

adam closed this issue

2026-01-05 14:50:13 +01:00

adam commented

2026-01-05 14:50:14 +01:00

@LGUG2Z commented on GitHub (May 20, 2024):

It looks like you're using a custom configuration directory.

You'll either have to change the runtime environment of startup apps to make sure any custom environment variables are loaded, or alternatively you can rerun the enable-autostart command and pass an absolute path to the configuration file.

@LGUG2Z commented on GitHub (May 20, 2024): It looks like you're using a custom configuration directory. You'll either have to change the runtime environment of startup apps to make sure any custom environment variables are loaded, or alternatively you can rerun the `enable-autostart` command and pass an absolute path to the configuration file.

adam commented

2026-01-05 14:50:14 +01:00