starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

[BUG]: Komorebi Fails to Execute Commands on Time (delayed execution up to 10-15sec) #667

New Issue
Open
opened 2026-01-05 14:52:15 +01:00 by adam · 12 comments
adam commented 2026-01-05 14:52:15 +01:00
Owner
Copy Link

Originally created by @loeiks on GitHub (Aug 21, 2025).

Summary

I didn't have this issue until I downloaded WSL (v2) and started using it on my Windows instead of powershell for my development things, but I didn't change anything for komorebi just installed the WSL and Ubuntu.

I also removed some dev tools (Go language, nvm etc.) I kept very few things such as Git because I'm not planning to run dev commands or tasks on Windows anymore.

But after I installed WSL and removed some dev tools/languages I started to see some delays on some calls, it's not happening always but it's not very rare too.

When I press a shortcut sometimes it takes 2-3sec to respond it responds in the end but it takes a long delay which is normally only few ms probably because I don't feel any delay normally.

It's like freezing, when I understand that call is delayed if I press more shortcuts all of them are waiting for the first one to execute and complete I guess and so others also doesn't work and after first one executes after that 2-3sec rest of them executes too.

It's just like freezing. I tried to run commands multiple times on terminal manually to see if that happens there to and I wasn't able to reproduce it in terminal (PowerShell) I launched WSL and I also ran commands there and I was able to get that delayed call only for two times in total out of like 100+ spams.

I'm not sure if WSL is the reason or if it's even related but this started after I installed it and removed some dev tools. I also removed and reinstalled komorebi via winget to see if it's resolves but no.

Another interesting part is, if I leave komorebi log open in a terminal session that delayed calls never happens currently I use komorebi while logs are on in a powershell terminal (via Windows Terminal app).

I tried to play with AHK scripts too but I don't think so they are the reason.

-> Update - 22 Aug

I also find out that this happens almost everytime after a long period of inactivity with komorebi, for example if I don't use any shortcut for like 30min-1hour this freezing delay happens almost always. Now I will try to see if it also happens while logs are on in a terminal.

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

{
  "$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/v0.1.37/schema.json",
  "animation": {
    "enabled": true,
    "fps": 200,
    "duration": 150,
    "style": "EaseInOutSine"
  },
  "cross_boundary_behaviour": "Monitor",
  "cross_monitor_move_behaviour": "Insert",
  "display_index_preferences": {
    "0": "AOCB205-5&2790121b&0&UID4353",
    "1": "MSI4BB4-5&2790121b&0&UID4356",
    "2": "ACR0673-5&2790121b&0&UID4352"
  },
  "bar_configurations": [
    "$Env:KOMOREBI_CONFIG_HOME/komorebi.bar.json",
    "$Env:KOMOREBI_CONFIG_HOME/komorebi.bar.2.json",
    "$Env:KOMOREBI_CONFIG_HOME/komorebi.bar.3.json"
  ],
  "border": false,
  "default_workspace_padding": 0,
  "default_container_padding": 0,
  "window_hiding_behaviour": "Cloak",
  "theme": {
    "palette": "Catppuccin",
    "name": "Macchiato",
    "accent": "Text",
    "auto_select_text": "Lavender",
    "auto_select_fill": "Lavender"
  },
  "mouse_follows_focus": false,
  "monitors": [
    {
      "workspaces": [
        {
          "name": "1",
          "layout": "BSP"
        },
        {
          "name": "2",
          "layout": "BSP"
        },
        {
          "name": "3",
          "layout": "BSP"
        },
        {
          "name": "4",
          "layout": "BSP"
        }
      ]
    },
    {
      "workspaces": [
        {
          "name": "5",
          "layout": "BSP"
        },
        {
          "name": "6",
          "layout": "BSP"
        },
        {
          "name": "7",
          "layout": "BSP"
        }
      ]
    },
    {
      "workspaces": [
        {
          "name": "8",
          "layout": "BSP"
        },
        {
          "name": "9",
          "layout": "BSP"
        },
        {
          "name": "0",
          "layout": "BSP"
        }
      ]
    }
  ],
  "resize_delta": 100,
  "floating_applications": [],
  "manage_rules": [],
  "app_specific_configuration_path": [
    "$Env:KOMOREBI_CONFIG_HOME/applications.json",
    "$Env:KOMOREBI_CONFIG_HOME/overwritten-applications.json"
  ]
}

Hotkey Configuration

#Requires AutoHotkey v2.0.2
#SingleInstance Force

; AHK Modifier Keys with Short Symbols:
; ^ = CTRL
; + = SHIFT
; ! = ALT
; # = WINDOWS

Komorebic(cmd) {
    try {
        RunWait("komorebic.exe " . cmd, , "Hide")
        return
    } catch Error as e {
        MsgBox(e)
    }
}

#Include ./Scripts/window.ahk
#Include ./Scripts/workspace.ahk
#Include ./Scripts/modes.ahk

; --------------------------------------------------
; Komorebi Management
; --------------------------------------------------

; Reload Configuration and AHK Script
#^r:: {
    Komorebic("reload-configuration")
    ToolTip("Reloaded")
}

; Pause/Unpause Komorebi
#^p:: Komorebic("toggle-pause")

; Stop and exit Komorebi
#^e:: Komorebic("stop --ahk --bar")

; Spawn new terminal with Warp
#Enter:: Run("C:\Program Files\Warp\warp.exe")

modes

#Requires AutoHotkey v2.0

/**
 * Simple input mode for komorebi commands
 * 
 * @param actions Actions keys as prop and actions as value
 * @param prompt Prompt text to display (optional)
 * @param exitOnAction Exit after action key is pressed once (optional)
 */
EnterMode(actions, prompt := "", exitOnAction := false) {
    /**@type {Gui} */
    static promptGui := "" ; Use static instead of local

    if (prompt) {
        promptGui := Gui("+ToolWindow -Caption AlwaysOnTop")
        promptGui.SetFont("s24", "Segoe UI")
        promptGui.Add("Text", "y12", prompt)
        promptGui.Show("AutoSize Center NA")
    }

    loop {
        ih := InputHook("M", "{Escape}{Enter}")
        ih.KeyOpt("{All}", "S")

        for key, _ in actions {
            ih.KeyOpt("{" . key . "}", "E")
        }

        ih.Start()
        ih.Wait()

        if (actions.Has(ih.EndKey)) {
            Komorebic(actions[ih.EndKey])
        }

        if (exitOnAction || ih.EndKey == "Enter" || ih.EndKey == "Escape") {
            promptGui.Hide()
            break
        } else {
            continue
        }
    }
}

; --------------------------------------------------
; Mode Definitions
; --------------------------------------------------

; Monitor swap (auto-exit)
#!c:: EnterMode(Map(
    "0", "swap-workspaces-with-monitor 0",
    "1", "swap-workspaces-with-monitor 1",
    "2", "swap-workspaces-with-monitor 2"
), "2 ◄ 0 ► 1", true)

; Window resize (continuous)
#!r:: EnterMode(Map(
    "Left", "resize-axis horizontal decrease",
    "Right", "resize-axis horizontal increase",
    "Up", "resize-axis vertical increase",
    "Down", "resize-axis vertical decrease"
), "Resize (←, ↑, ↓, →)", false)

window

#Requires AutoHotkey v2.0

; --------------------------------------------------
; Window Management
; --------------------------------------------------
#q:: Komorebic("close") ; Close (X) focused window
#m:: Komorebic("minimize") ; Minimize focused window
#f:: Komorebic("toggle-maximize") ; Toggle fullscreen for focused window
#t:: Komorebic("toggle-float") ; Toggle floating for focused window
#c:: Komorebic("toggle-monocle") ; Toggle monocle for focused window (use maximum space)

; --------------------------------------------------
; Move Windows
; --------------------------------------------------
#left:: Komorebic("move left")
#right:: Komorebic("move right")
#up:: Komorebic("move up")
#down:: Komorebic("move down")

; --------------------------------------------------
; Focus into Windows
; --------------------------------------------------
#!left:: Komorebic("focus left")
#!right:: Komorebic("focus right")
#!up:: Komorebic("focus up")
#!down:: Komorebic("focus down")

; --------------------------------------------------
; Stacking Management
; --------------------------------------------------
#+s:: Komorebic("stack-all")
#+!s:: Komorebic("unstack-all")
#+x:: Komorebic("cycle-stack next")

workspace

#Requires AutoHotkey v2.0

; --------------------------------------------------
; Workspace Switching
; --------------------------------------------------
#0:: Komorebic("focus-named-workspace 0")
#1:: Komorebic("focus-named-workspace 1")
#2:: Komorebic("focus-named-workspace 2")
#3:: Komorebic("focus-named-workspace 3")
#4:: Komorebic("focus-named-workspace 4")
#5:: Komorebic("focus-named-workspace 5")
#6:: Komorebic("focus-named-workspace 6")
#7:: Komorebic("focus-named-workspace 7")
#8:: Komorebic("focus-named-workspace 8")
#9:: Komorebic("focus-named-workspace 9")

#Numpad0:: Komorebic("focus-named-workspace 0")
#Numpad1:: Komorebic("focus-named-workspace 1")
#Numpad3:: Komorebic("focus-named-workspace 3")
#Numpad2:: Komorebic("focus-named-workspace 2")
#Numpad4:: Komorebic("focus-named-workspace 4")
#Numpad5:: Komorebic("focus-named-workspace 5")
#Numpad6:: Komorebic("focus-named-workspace 6")
#Numpad7:: Komorebic("focus-named-workspace 7")
#Numpad8:: Komorebic("focus-named-workspace 8")
#Numpad9:: Komorebic("focus-named-workspace 9")

#+Left:: Komorebic("cycle-workspace previous")
#+Right:: Komorebic("cycle-workspace next")

; --------------------------------------------------
; Move Windows to Workspaces
; --------------------------------------------------
#+1:: Komorebic("move-to-named-workspace 1")
#+2:: Komorebic("move-to-named-workspace 2")
#+3:: Komorebic("move-to-named-workspace 3")
#+4:: Komorebic("move-to-named-workspace 4")
#+5:: Komorebic("move-to-named-workspace 5")
#+6:: Komorebic("move-to-named-workspace 6")
#+7:: Komorebic("move-to-named-workspace 7")
#+8:: Komorebic("move-to-named-workspace 8")
#+9:: Komorebic("move-to-named-workspace 9")
#+0:: Komorebic("move-to-named-workspace 0")

;--------------------------------------------------
; Switch Between Last Used Workspaces (Alt+Tab)
; --------------------------------------------------
#d:: Komorebic("focus-last-workspace")

;--------------------------------------------------
; Move Workspaces to Monitors
; --------------------------------------------------
#space:: Komorebic("cycle-layout")

;--------------------------------------------------
; Move Workspaces to Monitors
; --------------------------------------------------
monitorOrder := [2, 0, 1]  ; Left, Main, Right
currentPos := 2

#+a:: {
    global currentPos, monitorOrder
    currentPos := Mod(currentPos - 2 + monitorOrder.Length, monitorOrder.Length) + 1
    Komorebic("move-workspace-to-monitor " monitorOrder[currentPos])
}

#+d:: {
    global currentPos, monitorOrder
    currentPos := Mod(currentPos, monitorOrder.Length) + 1
    Komorebic("move-workspace-to-monitor " monitorOrder[currentPos])
}

I split files to keep them organized.

Output of komorebic check

KOMOREBI_CONFIG_HOME detected: C:\Users\loeiks\loeiks\Configs\settings-sync\Apps\Komorebi

Looking for configuration files in C:\Users\loeiks\loeiks\Configs\settings-sync\Apps\Komorebi

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

No ~/.config/whkdrc found; you may not be able to control komorebi with your keyboard

Originally created by @loeiks on GitHub (Aug 21, 2025). ### Summary I didn't have this issue until I downloaded WSL (v2) and started using it on my Windows instead of powershell for my development things, but I didn't change anything for komorebi just installed the WSL and Ubuntu. I also removed some dev tools (Go language, nvm etc.) I kept very few things such as Git because I'm not planning to run dev commands or tasks on Windows anymore. But after I installed WSL and removed some dev tools/languages I started to see some delays on some calls, it's not happening always but it's not very rare too. When I press a shortcut sometimes it takes 2-3sec to respond it responds in the end but it takes a long delay which is normally only few ms probably because I don't feel any delay normally. It's like freezing, when I understand that call is delayed if I press more shortcuts all of them are waiting for the first one to execute and complete I guess and so others also doesn't work and after first one executes after that 2-3sec rest of them executes too. It's just like freezing. I tried to run commands multiple times on terminal manually to see if that happens there to and I wasn't able to reproduce it in terminal (PowerShell) I launched WSL and I also ran commands there and I was able to get that delayed call only for two times in total out of like 100+ spams. I'm not sure if WSL is the reason or if it's even related but this started after I installed it and removed some dev tools. I also removed and reinstalled komorebi via winget to see if it's resolves but no. Another interesting part is, if I leave komorebi log open in a terminal session that delayed calls never happens currently I use komorebi while logs are on in a powershell terminal (via Windows Terminal app). I tried to play with AHK scripts too but I don't think so they are the reason. -> Update - 22 Aug I also find out that this happens almost everytime after a long period of inactivity with komorebi, for example if I don't use any shortcut for like 30min-1hour this freezing delay happens almost always. Now I will try to see if it also happens while logs are on in a terminal. ### 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", "animation": { "enabled": true, "fps": 200, "duration": 150, "style": "EaseInOutSine" }, "cross_boundary_behaviour": "Monitor", "cross_monitor_move_behaviour": "Insert", "display_index_preferences": { "0": "AOCB205-5&2790121b&0&UID4353", "1": "MSI4BB4-5&2790121b&0&UID4356", "2": "ACR0673-5&2790121b&0&UID4352" }, "bar_configurations": [ "$Env:KOMOREBI_CONFIG_HOME/komorebi.bar.json", "$Env:KOMOREBI_CONFIG_HOME/komorebi.bar.2.json", "$Env:KOMOREBI_CONFIG_HOME/komorebi.bar.3.json" ], "border": false, "default_workspace_padding": 0, "default_container_padding": 0, "window_hiding_behaviour": "Cloak", "theme": { "palette": "Catppuccin", "name": "Macchiato", "accent": "Text", "auto_select_text": "Lavender", "auto_select_fill": "Lavender" }, "mouse_follows_focus": false, "monitors": [ { "workspaces": [ { "name": "1", "layout": "BSP" }, { "name": "2", "layout": "BSP" }, { "name": "3", "layout": "BSP" }, { "name": "4", "layout": "BSP" } ] }, { "workspaces": [ { "name": "5", "layout": "BSP" }, { "name": "6", "layout": "BSP" }, { "name": "7", "layout": "BSP" } ] }, { "workspaces": [ { "name": "8", "layout": "BSP" }, { "name": "9", "layout": "BSP" }, { "name": "0", "layout": "BSP" } ] } ], "resize_delta": 100, "floating_applications": [], "manage_rules": [], "app_specific_configuration_path": [ "$Env:KOMOREBI_CONFIG_HOME/applications.json", "$Env:KOMOREBI_CONFIG_HOME/overwritten-applications.json" ] } ``` ### Hotkey Configuration ```ahkv2 #Requires AutoHotkey v2.0.2 #SingleInstance Force ; AHK Modifier Keys with Short Symbols: ; ^ = CTRL ; + = SHIFT ; ! = ALT ; # = WINDOWS Komorebic(cmd) { try { RunWait("komorebic.exe " . cmd, , "Hide") return } catch Error as e { MsgBox(e) } } #Include ./Scripts/window.ahk #Include ./Scripts/workspace.ahk #Include ./Scripts/modes.ahk ; -------------------------------------------------- ; Komorebi Management ; -------------------------------------------------- ; Reload Configuration and AHK Script #^r:: { Komorebic("reload-configuration") ToolTip("Reloaded") } ; Pause/Unpause Komorebi #^p:: Komorebic("toggle-pause") ; Stop and exit Komorebi #^e:: Komorebic("stop --ahk --bar") ; Spawn new terminal with Warp #Enter:: Run("C:\Program Files\Warp\warp.exe") ``` --- modes ```ahkv2 #Requires AutoHotkey v2.0 /** * Simple input mode for komorebi commands * * @param actions Actions keys as prop and actions as value * @param prompt Prompt text to display (optional) * @param exitOnAction Exit after action key is pressed once (optional) */ EnterMode(actions, prompt := "", exitOnAction := false) { /**@type {Gui} */ static promptGui := "" ; Use static instead of local if (prompt) { promptGui := Gui("+ToolWindow -Caption AlwaysOnTop") promptGui.SetFont("s24", "Segoe UI") promptGui.Add("Text", "y12", prompt) promptGui.Show("AutoSize Center NA") } loop { ih := InputHook("M", "{Escape}{Enter}") ih.KeyOpt("{All}", "S") for key, _ in actions { ih.KeyOpt("{" . key . "}", "E") } ih.Start() ih.Wait() if (actions.Has(ih.EndKey)) { Komorebic(actions[ih.EndKey]) } if (exitOnAction || ih.EndKey == "Enter" || ih.EndKey == "Escape") { promptGui.Hide() break } else { continue } } } ; -------------------------------------------------- ; Mode Definitions ; -------------------------------------------------- ; Monitor swap (auto-exit) #!c:: EnterMode(Map( "0", "swap-workspaces-with-monitor 0", "1", "swap-workspaces-with-monitor 1", "2", "swap-workspaces-with-monitor 2" ), "2 ◄ 0 ► 1", true) ; Window resize (continuous) #!r:: EnterMode(Map( "Left", "resize-axis horizontal decrease", "Right", "resize-axis horizontal increase", "Up", "resize-axis vertical increase", "Down", "resize-axis vertical decrease" ), "Resize (←, ↑, ↓, →)", false) ``` window ```ahkv2 #Requires AutoHotkey v2.0 ; -------------------------------------------------- ; Window Management ; -------------------------------------------------- #q:: Komorebic("close") ; Close (X) focused window #m:: Komorebic("minimize") ; Minimize focused window #f:: Komorebic("toggle-maximize") ; Toggle fullscreen for focused window #t:: Komorebic("toggle-float") ; Toggle floating for focused window #c:: Komorebic("toggle-monocle") ; Toggle monocle for focused window (use maximum space) ; -------------------------------------------------- ; Move Windows ; -------------------------------------------------- #left:: Komorebic("move left") #right:: Komorebic("move right") #up:: Komorebic("move up") #down:: Komorebic("move down") ; -------------------------------------------------- ; Focus into Windows ; -------------------------------------------------- #!left:: Komorebic("focus left") #!right:: Komorebic("focus right") #!up:: Komorebic("focus up") #!down:: Komorebic("focus down") ; -------------------------------------------------- ; Stacking Management ; -------------------------------------------------- #+s:: Komorebic("stack-all") #+!s:: Komorebic("unstack-all") #+x:: Komorebic("cycle-stack next") ``` workspace ```ahkv2 #Requires AutoHotkey v2.0 ; -------------------------------------------------- ; Workspace Switching ; -------------------------------------------------- #0:: Komorebic("focus-named-workspace 0") #1:: Komorebic("focus-named-workspace 1") #2:: Komorebic("focus-named-workspace 2") #3:: Komorebic("focus-named-workspace 3") #4:: Komorebic("focus-named-workspace 4") #5:: Komorebic("focus-named-workspace 5") #6:: Komorebic("focus-named-workspace 6") #7:: Komorebic("focus-named-workspace 7") #8:: Komorebic("focus-named-workspace 8") #9:: Komorebic("focus-named-workspace 9") #Numpad0:: Komorebic("focus-named-workspace 0") #Numpad1:: Komorebic("focus-named-workspace 1") #Numpad3:: Komorebic("focus-named-workspace 3") #Numpad2:: Komorebic("focus-named-workspace 2") #Numpad4:: Komorebic("focus-named-workspace 4") #Numpad5:: Komorebic("focus-named-workspace 5") #Numpad6:: Komorebic("focus-named-workspace 6") #Numpad7:: Komorebic("focus-named-workspace 7") #Numpad8:: Komorebic("focus-named-workspace 8") #Numpad9:: Komorebic("focus-named-workspace 9") #+Left:: Komorebic("cycle-workspace previous") #+Right:: Komorebic("cycle-workspace next") ; -------------------------------------------------- ; Move Windows to Workspaces ; -------------------------------------------------- #+1:: Komorebic("move-to-named-workspace 1") #+2:: Komorebic("move-to-named-workspace 2") #+3:: Komorebic("move-to-named-workspace 3") #+4:: Komorebic("move-to-named-workspace 4") #+5:: Komorebic("move-to-named-workspace 5") #+6:: Komorebic("move-to-named-workspace 6") #+7:: Komorebic("move-to-named-workspace 7") #+8:: Komorebic("move-to-named-workspace 8") #+9:: Komorebic("move-to-named-workspace 9") #+0:: Komorebic("move-to-named-workspace 0") ;-------------------------------------------------- ; Switch Between Last Used Workspaces (Alt+Tab) ; -------------------------------------------------- #d:: Komorebic("focus-last-workspace") ;-------------------------------------------------- ; Move Workspaces to Monitors ; -------------------------------------------------- #space:: Komorebic("cycle-layout") ;-------------------------------------------------- ; Move Workspaces to Monitors ; -------------------------------------------------- monitorOrder := [2, 0, 1] ; Left, Main, Right currentPos := 2 #+a:: { global currentPos, monitorOrder currentPos := Mod(currentPos - 2 + monitorOrder.Length, monitorOrder.Length) + 1 Komorebic("move-workspace-to-monitor " monitorOrder[currentPos]) } #+d:: { global currentPos, monitorOrder currentPos := Mod(currentPos, monitorOrder.Length) + 1 Komorebic("move-workspace-to-monitor " monitorOrder[currentPos]) } ``` I split files to keep them organized. ### Output of komorebic check KOMOREBI_CONFIG_HOME detected: C:\Users\loeiks\loeiks\Configs\settings-sync\Apps\Komorebi Looking for configuration files in C:\Users\loeiks\loeiks\Configs\settings-sync\Apps\Komorebi Found komorebi.json; this file can be passed to the start command with the --config flag No ~/.config/whkdrc found; you may not be able to control komorebi with your keyboard
adam added the apps-behaving-badly label 2026-01-05 14:52:15 +01:00
adam commented 2026-01-05 14:52:16 +01:00
Author
Owner
Copy Link

@loeiks commented on GitHub (Sep 1, 2025):

Now I have this delay on almost every command out of 10, sometimes it's 2sec delay sometimes 5sec. I started saving logs in AHK to see how much it took to run komorebi command and I can see that it sometimes took 2, 3 or even 5 sec to complete.

I have no idea why is this happening.

@loeiks commented on GitHub (Sep 1, 2025): Now I have this delay on almost every command out of 10, sometimes it's 2sec delay sometimes 5sec. I started saving logs in AHK to see how much it took to run komorebi command and I can see that it sometimes took 2, 3 or even 5 sec to complete. I have no idea why is this happening.
adam commented 2026-01-05 14:52:16 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Sep 1, 2025):

This was not clear to me from your posts - is the delay in receiving and responding to the socket messages themselves? (ie. when you run komorebic whatever from a PowerShell prompt), or is the delay in dispatching the shell commands which send the socket messages?

@LGUG2Z commented on GitHub (Sep 1, 2025): This was not clear to me from your posts - is the delay in receiving and responding to the socket messages themselves? (ie. when you run `komorebic whatever` from a PowerShell prompt), or is the delay in dispatching the shell commands which send the socket messages?
adam commented 2026-01-05 14:52:16 +01:00
Author
Owner
Copy Link

@loeiks commented on GitHub (Sep 2, 2025):

When I run a komorebic command (doesn't matter what command) it's executed with a delay. For example;

  1. I press #1 which changes workspaces on my setup ->
  2. AHK runs komorebic.exe focus-named-workspace 1 ->
  3. And now I'm on workspace 1. (visual change)

Delay is on the second part, when a command runs sometimes it takes up to 10-15sec to actually react and do something and in that state any other command is ignored at all, while one of them is freezed/running.

A small log example:

06:14 PM - Komorebic Command: 'focus-named-workspace 3' took 79ms
06:17 PM - Komorebic Command: 'focus-named-workspace 0' took 78ms
06:19 PM - Komorebic Command: 'focus-named-workspace 3' took 94ms
06:22 PM - Komorebic Command: 'focus-named-workspace 0' took 12047ms
06:22 PM - Komorebic Command: 'focus-named-workspace 0' took 109ms
06:22 PM - Komorebic Command: 'focus-named-workspace 0' took 78ms
06:23 PM - Komorebic Command: 'focus-named-workspace 0' took 78ms
06:23 PM - Komorebic Command: 'focus-named-workspace 5' took 94ms

Normally commands takes 70ms on avg to execute and complete. But as you can see from above one command took 12sec to execute and complete.

I actually pressed maybe 20 times to the same shortcut but only one of them executed because when it's executing a command it doesn't execute any other requests (next commands are executed after that 12sec completed).

Basically my workspace just changed after 12sec.

What I have tested so far?

  1. This issue is resolved when I open up terminal and run komorebic.exe log while terminal up and running with this command I have no issue at all, I don't know why but I find this out because I wanted to check if there any errors and no there is no errors, but if komorebic.exe log is up and running there is not a single delayed command all of them runs and executes perfectly.
  2. If I only open terminal (no komorebi logs) it still happens.
  3. I tried to play with Windows Terminal app settings and did nothing.
  4. I installed PowerShell 7 to see if it changes anything, it did nothing too.
  5. I removed and reinstalled komorebi with winget and it didn't solve the issue too.

This issue started after I installed WSL (v2) I think there is a issue with this maybe some conflict or I don't know but this is just started after I installed WSL.

If there is a way to clean install komorebi let me know and let me do it, maybe it solves the issue.

AHK script for logging:

SaveLog(message) {
    return FileAppend(message, "C:\Users\loeiks\komorebi-logs.txt")
}

Komorebic(cmd) {
    startTime := A_TickCount
    if (ProcessExist("komorebi.exe")) {
        RunWait(Format("komorebic.exe {}", cmd), , "Hide")
        return SaveLog(
            Format("{} - Komorebic Command: '{}' took {}ms`n",
                FormatTime(A_Now, "hh:mm tt"), cmd, A_TickCount - startTime
            )
        )
    }
}

same issue was there before I updated Komorebic function to save logs and check for process so there is no issue with these at all, I just added them to see if delaying part was command or something else and it was the command itself clearly.

I suspect few things:

  • Is it possible that commands are somehow conflict with WSL and they are delayed because of that?
  • Is it possible that commands are executed after a long delay, actually not running very long (so it's actually not taking too much time to finish but takes time to start the process)?
  • Is it possible that is it related with slow startup time of powershell or terminal due to WSL?

Since this started after I installed WSL, I kinda think about these. I checked my drivers I re-installed komorebi and I don't think so there is a software or driver kind of issue and I suspect a conflict or a slow reaction from some kind of app that maybe komorebi depends on?

And another hint is when komorebic.exe log is running this is resolved, so all requests are maybe going into running instance and that's why commands aren't freezed/delayed and executed just as fast as it should be. And if this is the case I think it points that something is starting very slow sometimes and that's why some commands are taking too long to execute and run.

Another hint is, that delay is most likely happens when I don't run any command for some time (10min, 20min a bit long durations) it mostly (but not %100) happens in these cases. It also happens in other cases but when I wait long enough in the same state it's more likely to get a command executed with a long delay (at least 1-2 sec and up to 10-15sec based on my logs).

I hope I was able to explain things more clearly and point out my findings in a understandable way. I'm not a Rust developer so I don't know how things works under the hood but I wanted to talk about my assumptions.

@loeiks commented on GitHub (Sep 2, 2025): When I run a `komorebic` command (doesn't matter what command) it's executed with a delay. For example; 1. I press `#1` which changes workspaces on my setup -> 2. AHK runs `komorebic.exe focus-named-workspace 1` -> 3. And now I'm on workspace 1. (visual change) Delay is on the second part, when a command runs sometimes it takes up to 10-15sec to actually react and do something and in that state any other command is ignored at all, while one of them is freezed/running. A small log example: ```txt 06:14 PM - Komorebic Command: 'focus-named-workspace 3' took 79ms 06:17 PM - Komorebic Command: 'focus-named-workspace 0' took 78ms 06:19 PM - Komorebic Command: 'focus-named-workspace 3' took 94ms 06:22 PM - Komorebic Command: 'focus-named-workspace 0' took 12047ms 06:22 PM - Komorebic Command: 'focus-named-workspace 0' took 109ms 06:22 PM - Komorebic Command: 'focus-named-workspace 0' took 78ms 06:23 PM - Komorebic Command: 'focus-named-workspace 0' took 78ms 06:23 PM - Komorebic Command: 'focus-named-workspace 5' took 94ms ``` Normally commands takes 70ms on avg to execute and complete. But as you can see from above one command took 12sec to execute and complete. I actually pressed maybe 20 times to the same shortcut but only one of them executed because when it's executing a command it doesn't execute any other requests (next commands are executed after that 12sec completed). Basically my workspace just changed after 12sec. What I have tested so far? 1. This issue is resolved when I open up terminal and run `komorebic.exe log` while terminal up and running with this command I have no issue at all, I don't know why but I find this out because I wanted to check if there any errors and no there is no errors, but if `komorebic.exe log` is up and running there is not a single delayed command all of them runs and executes perfectly. 2. If I only open terminal (no komorebi logs) it still happens. 3. I tried to play with Windows Terminal app settings and did nothing. 4. I installed PowerShell 7 to see if it changes anything, it did nothing too. 5. I removed and reinstalled komorebi with `winget` and it didn't solve the issue too. This issue started after I installed WSL (v2) I think there is a issue with this maybe some conflict or I don't know but this is just started after I installed WSL. If there is a way to clean install komorebi let me know and let me do it, maybe it solves the issue. AHK script for logging: ```ahk SaveLog(message) { return FileAppend(message, "C:\Users\loeiks\komorebi-logs.txt") } Komorebic(cmd) { startTime := A_TickCount if (ProcessExist("komorebi.exe")) { RunWait(Format("komorebic.exe {}", cmd), , "Hide") return SaveLog( Format("{} - Komorebic Command: '{}' took {}ms`n", FormatTime(A_Now, "hh:mm tt"), cmd, A_TickCount - startTime ) ) } } ``` > same issue was there before I updated `Komorebic` function to save logs and check for process so there is no issue with these at all, I just added them to see if delaying part was command or something else and it was the command itself clearly. --- I suspect few things: - Is it possible that commands are somehow conflict with WSL and they are delayed because of that? - Is it possible that commands are executed after a long delay, actually not running very long (so it's actually not taking too much time to finish but takes time to start the process)? - Is it possible that is it related with slow startup time of powershell or terminal due to WSL? Since this started after I installed WSL, I kinda think about these. I checked my drivers I re-installed komorebi and I don't think so there is a software or driver kind of issue and I suspect a conflict or a slow reaction from some kind of app that maybe komorebi depends on? And another hint is when `komorebic.exe log` is running this is resolved, so all requests are maybe going into running instance and that's why commands aren't freezed/delayed and executed just as fast as it should be. And if this is the case I think it points that something is starting very slow sometimes and that's why some commands are taking too long to execute and run. Another hint is, that delay is most likely happens when I don't run any command for some time (10min, 20min a bit long durations) it mostly (but not %100) happens in these cases. It also happens in other cases but when I wait long enough in the same state it's more likely to get a command executed with a long delay (at least 1-2 sec and up to 10-15sec based on my logs). --- I hope I was able to explain things more clearly and point out my findings in a understandable way. I'm not a Rust developer so I don't know how things works under the hood but I wanted to talk about my assumptions.
adam commented 2026-01-05 14:52:17 +01:00
Author
Owner
Copy Link

@loeiks commented on GitHub (Sep 7, 2025):

I will try to use whkd instead of AHK, if it doesn't solve the issue;

I will do factory reset to my Windows and see if it fixes this issue because I kinda tried everything to fix this. If it's not fixed I think there is an issue either how AHK runs things or a BUG inside komorebi.

@loeiks commented on GitHub (Sep 7, 2025): I will try to use whkd instead of AHK, if it doesn't solve the issue; I will do factory reset to my Windows and see if it fixes this issue because I kinda tried everything to fix this. If it's not fixed I think there is an issue either how AHK runs things or a BUG inside komorebi.
adam commented 2026-01-05 14:52:19 +01:00
Author
Owner
Copy Link

@loeiks commented on GitHub (Sep 8, 2025):

I have tried to use whkd instead of AHK to see if something wrong with AHK but not even with whkd I have the same issue what I also see that I didn't check before.

Whenever commands are running in normal speed (50-70ms) I don't see any process spawned in task manager probably because it's spawned and completed it's task very fast.

When there is a delay a new process komorebic.exe spawns and stays there with komorebi.exe until command is executed and task is completed so I'm now sure that there is no issue something like cold start, delay is directly happens inside komorebi.

I tried to shutdown WSL and any VM service/process and see if that delay will happen again so more understand if the issue is related with WSL installation, but no even while WSL is all shutdown (I was also monitoring processes of WSL it's not auto launched or so) same delayed execution happened.

A new interesting part is that delay was much more rare before but now it happens almost every 10 min or 5 min like at least 1 of my hotkey presses out of 10 is delayed.

There might be something with Windows updates too, so I will go and do a factory reset and see if anything will change if not I don't know what is the reason.

I don't think so this is a BUG inside the software but more like a local issue on my end I follow up this issue to get this into Google searches so if anyone gets into same state maybe they can read this.

@loeiks commented on GitHub (Sep 8, 2025): I have tried to use whkd instead of AHK to see if something wrong with AHK but not even with whkd I have the same issue what I also see that I didn't check before. Whenever commands are running in normal speed (50-70ms) I don't see any process spawned in task manager probably because it's spawned and completed it's task very fast. When there is a delay a new process `komorebic.exe` spawns and stays there with `komorebi.exe` until command is executed and task is completed so I'm now sure that there is no issue something like cold start, delay is directly happens inside komorebi. I tried to shutdown WSL and any VM service/process and see if that delay will happen again so more understand if the issue is related with WSL installation, but no even while WSL is all shutdown (I was also monitoring processes of WSL it's not auto launched or so) same delayed execution happened. A new interesting part is that delay was much more rare before but now it happens almost every 10 min or 5 min like at least 1 of my hotkey presses out of 10 is delayed. There might be something with Windows updates too, so I will go and do a factory reset and see if anything will change if not I don't know what is the reason. I don't think so this is a BUG inside the software but more like a local issue on my end I follow up this issue to get this into Google searches so if anyone gets into same state maybe they can read this.
adam commented 2026-01-05 14:52:19 +01:00
Author
Owner
Copy Link

@loeiks commented on GitHub (Sep 8, 2025):

10:45 AM - Komorebic Command: 'focus-named-workspace 1' took 78ms
10:45 AM - Komorebic Command: 'focus-named-workspace 2' took 78ms
10:45 AM - Komorebic Command: 'focus-named-workspace 1' took 62ms
11:29 AM - Komorebic Command: 'focus-named-workspace 2' took 63ms
11:29 AM - Komorebic Command: 'focus-named-workspace 1' took 5344ms
11:30 AM - Komorebic Command: 'focus-named-workspace 3' took 63ms
11:30 AM - Komorebic Command: 'focus-named-workspace 1' took 78ms
11:30 AM - Komorebic Command: 'focus-named-workspace 2' took 62ms
11:30 AM - Komorebic Command: 'focus-named-workspace 3' took 63ms
11:30 AM - Komorebic Command: 'focus-named-workspace 1' took 78ms
11:30 AM - Komorebic Command: 'focus-named-workspace 2' took 62ms
11:30 AM - Komorebic Command: 'focus-named-workspace 3' took 78ms
11:30 AM - Komorebic Command: 'focus-named-workspace 1' took 62ms
11:37 AM - Komorebic Command: 'focus-named-workspace 2' took 1141ms
11:37 AM - Komorebic Command: 'focus-named-workspace 2' took 78ms
11:37 AM - Komorebic Command: 'focus-named-workspace 3' took 63ms
11:37 AM - Komorebic Command: 'focus-named-workspace 1' took 63ms

Example logs: just after few minutes same delay happens again and again. Interesting.

@loeiks commented on GitHub (Sep 8, 2025): ```txt 10:45 AM - Komorebic Command: 'focus-named-workspace 1' took 78ms 10:45 AM - Komorebic Command: 'focus-named-workspace 2' took 78ms 10:45 AM - Komorebic Command: 'focus-named-workspace 1' took 62ms 11:29 AM - Komorebic Command: 'focus-named-workspace 2' took 63ms 11:29 AM - Komorebic Command: 'focus-named-workspace 1' took 5344ms 11:30 AM - Komorebic Command: 'focus-named-workspace 3' took 63ms 11:30 AM - Komorebic Command: 'focus-named-workspace 1' took 78ms 11:30 AM - Komorebic Command: 'focus-named-workspace 2' took 62ms 11:30 AM - Komorebic Command: 'focus-named-workspace 3' took 63ms 11:30 AM - Komorebic Command: 'focus-named-workspace 1' took 78ms 11:30 AM - Komorebic Command: 'focus-named-workspace 2' took 62ms 11:30 AM - Komorebic Command: 'focus-named-workspace 3' took 78ms 11:30 AM - Komorebic Command: 'focus-named-workspace 1' took 62ms 11:37 AM - Komorebic Command: 'focus-named-workspace 2' took 1141ms 11:37 AM - Komorebic Command: 'focus-named-workspace 2' took 78ms 11:37 AM - Komorebic Command: 'focus-named-workspace 3' took 63ms 11:37 AM - Komorebic Command: 'focus-named-workspace 1' took 63ms ``` Example logs: just after few minutes same delay happens again and again. Interesting.
adam commented 2026-01-05 14:52:19 +01:00
Author
Owner
Copy Link

@loeiks commented on GitHub (Sep 8, 2025):

I just did a factory reset to my Windows installed everything except WSL, this time I used scoop instead of winget too (this probably won't change anything but I just mention it).

I will use my pc just like this for some time (probably not more than 12-24 hours) and I will see if that delayed thing happens again, if not then I will install WSL and see if anything changes after WSL installed.

I didn't change anything at all except:

  • I removed date from main bar because I don't want it there anymore not related with this issue.
  • Before I had my env variables in powershell profile (KOMOREBI_CONFIG_HOME was also in user variables and powershell env) I removed them and instead I only added them into user env variables:
KOMOREBI_AHK_EXE = "AutoHotkey64.exe"
KOMOREBI_CONFIG_HOME = "C:\Users\loeiks\loeiks\Configs\settings-sync\Apps\Komorebi"

Windows is up to date and probably in the same state before.
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.26100 N/A Build 26100

Yes it's same with the time I created this issue.

@loeiks commented on GitHub (Sep 8, 2025): I just did a factory reset to my Windows installed everything except WSL, this time I used scoop instead of winget too (this probably won't change anything but I just mention it). I will use my pc just like this for some time (probably not more than 12-24 hours) and I will see if that delayed thing happens again, if not then I will install WSL and see if anything changes after WSL installed. I didn't change anything at all except: - I removed date from main bar because I don't want it there anymore not related with this issue. - Before I had my env variables in powershell profile (KOMOREBI_CONFIG_HOME was also in user variables and powershell env) I removed them and instead I only added them into user env variables: ``` KOMOREBI_AHK_EXE = "AutoHotkey64.exe" KOMOREBI_CONFIG_HOME = "C:\Users\loeiks\loeiks\Configs\settings-sync\Apps\Komorebi" ``` Windows is up to date and probably in the same state before. OS Name: Microsoft Windows 11 Pro OS Version: 10.0.26100 N/A Build 26100 Yes it's same with the time I created this issue.
adam commented 2026-01-05 14:52:19 +01:00
Author
Owner
Copy Link

@loeiks commented on GitHub (Sep 17, 2025):

It's been almost 10 days after clean install of Windows and other apps, and I didn't have this issue. I wasn't able to fix it with many tries on different things but looks like it's resolved itself so it was a local issue as I understand and might introduce after installing WSL and removing some dev tools from Windows.

I still don't know what was the exact reason but looks like it's solved, anyone you can't fix it I recommend a clean install of Windows. If anything changes I'll comment here but for now I'll close this since I think it wasn't a BUG but more of a interesting issue that I wasn't able to fix until I clean install Windows again.

@loeiks commented on GitHub (Sep 17, 2025): It's been almost 10 days after clean install of Windows and other apps, and I didn't have this issue. I wasn't able to fix it with many tries on different things but looks like it's resolved itself so it was a local issue as I understand and might introduce after installing WSL and removing some dev tools from Windows. I still don't know what was the exact reason but looks like it's solved, anyone you can't fix it I recommend a clean install of Windows. If anything changes I'll comment here but for now I'll close this since I think it wasn't a BUG but more of a interesting issue that I wasn't able to fix until I clean install Windows again.
adam commented 2026-01-05 14:52:19 +01:00
Author
Owner
Copy Link

@loeiks commented on GitHub (Oct 15, 2025):

After a long time I slowly started to have the same issue again. Two times happened today and yesterday commands takes 7-8sec to complete, only two times happened in two days but it had started like that before as well. Probably it'll happen more often in the upcoming days.

So this should be a BUG in the komorebi I think, because not even clean format helped to solve the issue permanently as it seems right now. I will report back if it'll start happening more often just like before or was it just a very rare case.

09:49 PM - Komorebic Command: 'focus-named-workspace 1' took 79ms
09:49 PM - Komorebic Command: 'focus-named-workspace 1' took 78ms
09:50 PM - Komorebic Command: 'focus-named-workspace 3' took 94ms
11:46 PM - Komorebic Command: 'focus-named-workspace 1' took 93ms
11:51 PM - Komorebic Command: 'focus-named-workspace 2' took 93ms
11:24 AM - Komorebic Command: 'move-to-named-workspace 2' took 171ms
11:24 AM - Komorebic Command: 'focus-named-workspace 1' took 78ms
11:24 AM - Komorebic Command: 'focus-named-workspace 2' took 94ms
11:24 AM - Komorebic Command: 'focus-named-workspace 3' took 93ms
11:24 AM - Komorebic Command: 'focus-named-workspace 1' took 79ms
11:24 AM - Komorebic Command: 'focus-named-workspace 2' took 78ms
11:24 AM - Komorebic Command: 'focus-named-workspace 3' took 94ms
01:44 PM - Komorebic Command: 'focus-named-workspace 2' took 7360ms
01:49 PM - Komorebic Command: 'focus-named-workspace 1' took 93ms

These are logs I collect and save to .txt file to see how much delayed a command. When I did the clean install and re-installed the komorebi I had 60-70ms avg on commands now it's around 95-100ms which shows that commands took more time to execute over time for some reason. Sometimes average was even 40-50ms before, right now it's 90-100ms.

This might be also a helpful insight when debugging idk. I think something is conflicting with komorebi but I don't know what.

@loeiks commented on GitHub (Oct 15, 2025): After a long time I slowly started to have the same issue again. Two times happened today and yesterday commands takes 7-8sec to complete, only two times happened in two days but it had started like that before as well. Probably it'll happen more often in the upcoming days. So this should be a BUG in the komorebi I think, because not even clean format helped to solve the issue permanently as it seems right now. I will report back if it'll start happening more often just like before or was it just a very rare case. ``` 09:49 PM - Komorebic Command: 'focus-named-workspace 1' took 79ms 09:49 PM - Komorebic Command: 'focus-named-workspace 1' took 78ms 09:50 PM - Komorebic Command: 'focus-named-workspace 3' took 94ms 11:46 PM - Komorebic Command: 'focus-named-workspace 1' took 93ms 11:51 PM - Komorebic Command: 'focus-named-workspace 2' took 93ms 11:24 AM - Komorebic Command: 'move-to-named-workspace 2' took 171ms 11:24 AM - Komorebic Command: 'focus-named-workspace 1' took 78ms 11:24 AM - Komorebic Command: 'focus-named-workspace 2' took 94ms 11:24 AM - Komorebic Command: 'focus-named-workspace 3' took 93ms 11:24 AM - Komorebic Command: 'focus-named-workspace 1' took 79ms 11:24 AM - Komorebic Command: 'focus-named-workspace 2' took 78ms 11:24 AM - Komorebic Command: 'focus-named-workspace 3' took 94ms 01:44 PM - Komorebic Command: 'focus-named-workspace 2' took 7360ms 01:49 PM - Komorebic Command: 'focus-named-workspace 1' took 93ms ``` These are logs I collect and save to .txt file to see how much delayed a command. When I did the clean install and re-installed the komorebi I had 60-70ms avg on commands now it's around 95-100ms which shows that commands took more time to execute over time for some reason. Sometimes average was even 40-50ms before, right now it's 90-100ms. This might be also a helpful insight when debugging idk. I think something is conflicting with komorebi but I don't know what.
adam commented 2026-01-05 14:52:19 +01:00
Author
Owner
Copy Link

@loeiks commented on GitHub (Oct 19, 2025):

Found the issue, actually I had to think that before but I never thought that it could be the "Faceit AC" which is a anti-cheat application. It doesn't matter if app is open or not because it works on kernel-level so it scans everything. After I removed Faceit AC I didn't have any delayed executions also all of the commands started to work faster reduced from 90-100ms to 40-60ms again.

I will create a ticket about it at Faceit. But who uses Faceit AC to play CS2 should know that Komorebi will have delayed executions, workaround to solve this issue is keeping komorebi log open so process stays hot and AC doesn't scan it every time a command fired.

Example log when Faceit AC is installed but not even running (I mean application is not running)

11:24 AM - Komorebic Command: 'focus-named-workspace 3' took 94ms
01:44 PM - Komorebic Command: 'focus-named-workspace 2' took 7360ms (7sec delayed)
01:49 PM - Komorebic Command: 'focus-named-workspace 1' took 93ms
01:49 PM - Komorebic Command: 'focus-named-workspace 2' took 94ms
01:49 PM - Komorebic Command: 'focus-named-workspace 3' took 78ms
01:49 PM - Komorebic Command: 'focus-named-workspace 1' took 78ms
01:49 PM - Komorebic Command: 'focus-named-workspace 2' took 94ms
01:49 PM - Komorebic Command: 'focus-named-workspace 3' took 78ms
01:49 PM - Komorebic Command: 'focus-named-workspace 2' took 93ms
01:55 PM - Komorebic Command: 'focus-named-workspace 1' took 19343ms (19sec delayed)

Example log after removing Faceit AC from the system and cleaning regedit keys:

04:36 PM - Komorebic Command: 'focus-named-workspace 1' took 62ms
04:36 PM - Komorebic Command: 'focus-named-workspace 2' took 47ms
04:38 PM - Komorebic Command: 'focus-named-workspace 1' took 63ms
04:41 PM - Komorebic Command: 'focus-named-workspace 2' took 63ms
04:42 PM - Komorebic Command: 'focus-named-workspace 2' took 47ms
04:42 PM - Komorebic Command: 'focus-named-workspace 1' took 47ms
04:42 PM - Komorebic Command: 'focus-named-workspace 6' took 63ms
04:43 PM - Komorebic Command: 'focus-named-workspace 2' took 63ms
04:44 PM - Komorebic Command: 'focus-named-workspace 1' took 47ms
04:50 PM - Komorebic Command: 'focus-named-workspace 3' took 47ms
04:58 PM - Komorebic Command: 'focus-named-workspace 1' took 47ms

Which is clearly faster even in "non-delayed" executions. This can be marked as a "known-issue". I'm not sure if the cause is a BUG inside Komorebi or just how Faceit AC works and scans everything but I'm sure that the reason was Faceit AC not just because issue is resolved after I removed it, also it started just after one day when I installed it. Also tried many other things to understand the root cause and solve the issue and none of them had worked until this one.

-> https://www.faceit.com/en/anti-cheat (this is the app)

@loeiks commented on GitHub (Oct 19, 2025): **Found the issue,** actually I had to think that before but I never thought that it could be the "Faceit AC" which is a anti-cheat application. It doesn't matter if app is open or not because it works on kernel-level so it scans everything. After I removed Faceit AC I didn't have any delayed executions also all of the commands started to work faster reduced from 90-100ms to 40-60ms again. I will create a ticket about it at Faceit. But who uses Faceit AC to play CS2 should know that Komorebi will have delayed executions, workaround to solve this issue is keeping `komorebi log` open so process stays hot and AC doesn't scan it every time a command fired. Example log when Faceit AC is installed but not even running (I mean application is not running) ``` 11:24 AM - Komorebic Command: 'focus-named-workspace 3' took 94ms 01:44 PM - Komorebic Command: 'focus-named-workspace 2' took 7360ms (7sec delayed) 01:49 PM - Komorebic Command: 'focus-named-workspace 1' took 93ms 01:49 PM - Komorebic Command: 'focus-named-workspace 2' took 94ms 01:49 PM - Komorebic Command: 'focus-named-workspace 3' took 78ms 01:49 PM - Komorebic Command: 'focus-named-workspace 1' took 78ms 01:49 PM - Komorebic Command: 'focus-named-workspace 2' took 94ms 01:49 PM - Komorebic Command: 'focus-named-workspace 3' took 78ms 01:49 PM - Komorebic Command: 'focus-named-workspace 2' took 93ms 01:55 PM - Komorebic Command: 'focus-named-workspace 1' took 19343ms (19sec delayed) ``` Example log after removing Faceit AC from the system and cleaning regedit keys: ``` 04:36 PM - Komorebic Command: 'focus-named-workspace 1' took 62ms 04:36 PM - Komorebic Command: 'focus-named-workspace 2' took 47ms 04:38 PM - Komorebic Command: 'focus-named-workspace 1' took 63ms 04:41 PM - Komorebic Command: 'focus-named-workspace 2' took 63ms 04:42 PM - Komorebic Command: 'focus-named-workspace 2' took 47ms 04:42 PM - Komorebic Command: 'focus-named-workspace 1' took 47ms 04:42 PM - Komorebic Command: 'focus-named-workspace 6' took 63ms 04:43 PM - Komorebic Command: 'focus-named-workspace 2' took 63ms 04:44 PM - Komorebic Command: 'focus-named-workspace 1' took 47ms 04:50 PM - Komorebic Command: 'focus-named-workspace 3' took 47ms 04:58 PM - Komorebic Command: 'focus-named-workspace 1' took 47ms ``` Which is clearly faster even in "non-delayed" executions. This can be marked as a "known-issue". I'm not sure if the cause is a BUG inside Komorebi or just how Faceit AC works and scans everything but I'm sure that the reason was Faceit AC not just because issue is resolved after I removed it, also it started just after one day when I installed it. Also tried many other things to understand the root cause and solve the issue and none of them had worked until this one. -> https://www.faceit.com/en/anti-cheat (this is the app)
adam commented 2026-01-05 14:52:19 +01:00
Author
Owner
Copy Link

@loeiks commented on GitHub (Oct 22, 2025):

I created a ticket on Faceit, about this issue and they are not going to update their software as support says. So just let anyone know that if Faceit AC and Komorebi installed together only workaround I found is keeping komorebi log open to keep process hot so AC won't scan new processes and delay commands.

On the other hand I'm not sure if this can happen but you might get banned due to Komorebi on Faceit. I don't know if this can be fixed from the komorebi side with a optional flag to keep process on etc. But if possible that would be good :)

Other than Faceit AC you might also have a similar software which might create the same issue.

@loeiks commented on GitHub (Oct 22, 2025): I created a ticket on Faceit, about this issue and they are not going to update their software as support says. So just let anyone know that if Faceit AC and Komorebi installed together only workaround I found is keeping `komorebi log` open to keep process hot so AC won't scan new processes and delay commands. On the other hand I'm not sure if this can happen but you might get banned due to Komorebi on Faceit. I don't know if this can be fixed from the komorebi side with a optional flag to keep process on etc. But if possible that would be good :) > Other than Faceit AC you might also have a similar software which might create the same issue.
adam commented 2026-01-05 14:52:19 +01:00
Author
Owner
Copy Link

@loeiks commented on GitHub (Dec 15, 2025):

Probably fixed the issue will create PR after testing everything correctly.

@loeiks commented on GitHub (Dec 15, 2025): Probably fixed the issue will create PR after testing everything correctly.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label apps-behaving-badly
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#667
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?