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

[FEAT]: Open programs on specific monitors #603

New Issue
Closed
opened 2026-01-05 14:51:52 +01:00 by adam · 27 comments
adam commented 2026-01-05 14:51:52 +01:00
Owner
Copy Link

Originally created by @Skyppex on GitHub (Apr 22, 2025).

Eligibility

Individual Commercial Use License

Suggestion

I'd like to configure komorebi to open certain applications, such as Spotify, Slack, my browser, my code editor, and my terminal on specific monitors.

By using the display_index_preferences and some new config stuff i'd like to do this in my komorebi.json:

{
  "display_index_preferences": {
    ... lets say i have 2 monitors :)
  },
  "monitors": [
    "workspaces": ...
    "initial_program_rules": [
      {
        "display_index": "0",
        "id": "Spotify.exe",
        "kind": "Exe",
        "matching_strategy": "Equals"
      },
      {
        "display_index": "1",
        "id": "Slack.exe",
        "kind": "Exe",
        "matching_strategy": "Equals"
      }
    ]
  ]
}

additionally it would be great if a specific monitor automatically stacked programs. that feels like a different feature request though, but i'll mention it here in case thats already possible and i haven't found out how :)

Alternatives Considered

i've tried using the initial_named_workspace_rules.
i configured each monitor to have a single, unique workspace associated with it, but when launching the app, it opens in the focues monitor and gets hidden so that didn't really work as intended

Originally created by @Skyppex on GitHub (Apr 22, 2025). ### Eligibility Individual Commercial Use License ### Suggestion I'd like to configure komorebi to open certain applications, such as Spotify, Slack, my browser, my code editor, and my terminal on specific monitors. By using the display_index_preferences and some new config stuff i'd like to do this in my komorebi.json: ```json { "display_index_preferences": { ... lets say i have 2 monitors :) }, "monitors": [ "workspaces": ... "initial_program_rules": [ { "display_index": "0", "id": "Spotify.exe", "kind": "Exe", "matching_strategy": "Equals" }, { "display_index": "1", "id": "Slack.exe", "kind": "Exe", "matching_strategy": "Equals" } ] ] } ``` additionally it would be great if a specific monitor automatically stacked programs. that feels like a different feature request though, but i'll mention it here in case thats already possible and i haven't found out how :) ### Alternatives Considered i've tried using the initial_named_workspace_rules. i configured each monitor to have a single, unique workspace associated with it, but when launching the app, it opens in the focues monitor and gets hidden so that didn't really work as intended
adam added the enhancement label 2026-01-05 14:51:52 +01:00
adam closed this issue 2026-01-05 14:51:52 +01:00
adam commented 2026-01-05 14:51:52 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 22, 2025):

Feature requests on this repository are only open to current GitHub sponsors on the $5/month tier and above, people with a valid individual commercial use license, and approved contributors.
This issue has been automatically closed until one of those pre-requisites can be validated.

@github-actions[bot] commented on GitHub (Apr 22, 2025): Feature requests on this repository are only open to current [GitHub sponsors](https://github.com/sponsors/LGUG2Z) on the $5/month tier and above, people with a valid [individual commercial use license](https://lgug2z.com/software/komorebi), and approved contributors. This issue has been automatically closed until one of those pre-requisites can be validated.
adam commented 2026-01-05 14:51:53 +01:00
Author
Owner
Copy Link

@Skyppex commented on GitHub (Apr 22, 2025):

just to keep track of everything, i was given a solution in the discord:

Image

transcription:

alex-ds13 — 12:18
You can already do that with the "workspace_rules": and "initial_workspace_rules":. Any window that matches one of this rules will be moved to the workspace that contains that rule. When you say that the window disappears, that is probably because it was moved to the workspace for which you defined that rule but that workspace is not currently focused. If you focus that workspace you will see the window there!

You just need to embrace the workspaces and learn to properly use them! To me the best feature that komorebi has (or any tiling window manager like it..) is the workspaces! They let you organize your desktop much better.

does this actually cover my use case? if so, what would this config look like?

@Skyppex commented on GitHub (Apr 22, 2025): just to keep track of everything, i was given a solution in the discord: ![Image](https://github.com/user-attachments/assets/57a7bbd7-b578-4821-88eb-a40b922a34d7) transcription: > alex-ds13 — 12:18 You can already do that with the "workspace_rules": and "initial_workspace_rules":. Any window that matches one of this rules will be moved to the workspace that contains that rule. When you say that the window disappears, that is probably because it was moved to the workspace for which you defined that rule but that workspace is not currently focused. If you focus that workspace you will see the window there! > >You just need to embrace the workspaces and learn to properly use them! To me the best feature that komorebi has (or any tiling window manager like it..) is the workspaces! They let you organize your desktop much better. does this actually cover my use case? if so, what would this config look like?
adam commented 2026-01-05 14:51:53 +01:00
Author
Owner
Copy Link

@CtByte commented on GitHub (Apr 22, 2025):

... if so, what would this config look like?

You choose a workspace for the app to open on, then add the workspace rules.

workspace_rules will not let you move the app to another workspace, while initial_workspace_rules will let you.

(Might be important to note that Komorebi cannot spawn a window on a workspace/monitor, it will move it after it was spawned. Sometimes the bar cannot keep up with this and the app might appear on the wrong workspace first. Or if you are on the Personal workspace and open Chrome, it might just look like it did not open, however it was moved to the Work workspace).

      "workspaces": [
        {
          "name": "Personal",
          "layout": "BSP"
        },
        {
          "name": "Work",
          "layout": "BSP",
          "initial_workspace_rules": [
            {
              "kind": "Exe",
              "id": "chrome.exe",
              "matching_strategy": "Equals"
            }
          ]
        }
      ]
@CtByte commented on GitHub (Apr 22, 2025): >... if so, what would this config look like? You choose a workspace for the app to open on, then add the [workspace rules](https://komorebi.lgug2z.com/schema#monitors_items_workspaces_items_initial_workspace_rules). `workspace_rules` will not let you move the app to another workspace, while `initial_workspace_rules` will let you. (Might be important to note that Komorebi cannot spawn a window on a workspace/monitor, it will move it after it was spawned. Sometimes the bar cannot keep up with this and the app might appear on the wrong workspace first. Or if you are on the `Personal` workspace and open Chrome, it might just look like it did not open, however it was moved to the `Work` workspace). ```json "workspaces": [ { "name": "Personal", "layout": "BSP" }, { "name": "Work", "layout": "BSP", "initial_workspace_rules": [ { "kind": "Exe", "id": "chrome.exe", "matching_strategy": "Equals" } ] } ] ```
adam commented 2026-01-05 14:51:53 +01:00
Author
Owner
Copy Link

@Skyppex commented on GitHub (Apr 22, 2025):

@CtByte
Your config seems to work, but i'ts not exactly my use case.
I'm trying to just have a single workspace per monitor and assign specific apps to these workspaces.
I put Spotify.exe on the workspace for monitor 2:

    {
      "workspaces": [
        {
          "name": "Center Monitor", // index 0
          "layout": "VerticalStack"
        }
      ]
    },
    {
      "workspaces": [
        {
          "name": "Right Monitor", // index 1
          "layout": "VerticalStack"
        }
      ]
    },
    {
      "workspaces": [
        {
          "name": "Left Monitor", // index 2
          "layout": "VerticalStack",
          "initial_workspace_rules": [
            {
              "kind": "Exe",
              "id": "Spotify.exe",
              "matching_strategy": "Equals"
            }
          ]
        }
      ]
    }

Focus monitor 0, and open Spotify, it quickly flashes on monitor 0 and vanishes. The layout on monitor 0 has not changed which is expected.

The layout on monitor two changes as soon as its focused showing that Spotify should be on the right half of the screen (using the VerticalStack layout), and the left half is what was there before. The right half is, however, blank; just showing my desktop background.

Image

When i use Alt+Tab to focus spotify it appears on monitor 0 instead of monitor 2 and changes that layout (also VerticalStack) so that is appears on the right half and the rest is pushed to the left half.

Note:
While writing this comment, it has started working as i want for spotify most of the time.
It seems to be a little unstable though as it doesn't work every single time.
I'm noticing some other issues along with this where the app is moved, but ends up being too large and bleeds from the Left Monitor to the Center Monitor.
I can submit a separate bug report for that though :)

@Skyppex commented on GitHub (Apr 22, 2025): @CtByte Your config seems to work, but i'ts not exactly my use case. I'm trying to just have a single workspace per monitor and assign specific apps to these workspaces. I put Spotify.exe on the workspace for monitor 2: ```json { "workspaces": [ { "name": "Center Monitor", // index 0 "layout": "VerticalStack" } ] }, { "workspaces": [ { "name": "Right Monitor", // index 1 "layout": "VerticalStack" } ] }, { "workspaces": [ { "name": "Left Monitor", // index 2 "layout": "VerticalStack", "initial_workspace_rules": [ { "kind": "Exe", "id": "Spotify.exe", "matching_strategy": "Equals" } ] } ] } ``` Focus monitor 0, and open Spotify, it quickly flashes on monitor 0 and vanishes. The layout on monitor 0 has not changed which is expected. The layout on monitor two changes as soon as its focused showing that Spotify should be on the right half of the screen (using the VerticalStack layout), and the left half is what was there before. The right half is, however, blank; just showing my desktop background. ![Image](https://github.com/user-attachments/assets/f974f1d3-8825-40e5-bfb3-36f20844e533) When i use Alt+Tab to focus spotify it appears on monitor 0 instead of monitor 2 and changes that layout (also VerticalStack) so that is appears on the right half and the rest is pushed to the left half. Note: While writing this comment, it has started working as i want for spotify most of the time. It seems to be a little unstable though as it doesn't work every single time. I'm noticing some other issues along with this where the app is moved, but ends up being too large and bleeds from the `Left Monitor` to the `Center Monitor`. I can submit a separate bug report for that though :)
adam commented 2026-01-05 14:51:53 +01:00
Author
Owner
Copy Link

@CtByte commented on GitHub (Apr 22, 2025):

@Skyppex As I mentioned, Komorebi moves a window after it opened. If you are on Center Monitor and open Spotify, this is what happens:

  • Windows opens Spotify on the Center Monitor or whereever it decides to open it
  • Komorebi manages the window, adds it to your Center Monitor workspace using the layout
  • Komorebi looks for workspace rules and finds the rule and applies it to Spotify
  • Komorebi sends Spotify from the Center Monitor to Left Monitor <= This is where you see the flash
  • this is where the layout probably could not update soon enough, as Spotify was added and removed very quickly. A retile should solve the issue
  • Komorebi stays on Center Monitor

@LGUG2Z when Komorebi sends the window to another workspace it does not seem to apply workspace layout, right? So that is why the window is not resized and can "bleed through" monitors?

@CtByte commented on GitHub (Apr 22, 2025): @Skyppex As I mentioned, Komorebi moves a window after it opened. If you are on `Center Monitor` and open Spotify, this is what happens: - Windows opens Spotify on the `Center Monitor` or whereever it decides to open it - Komorebi manages the window, adds it to your `Center Monitor` workspace using the layout - Komorebi looks for workspace rules and finds the rule and applies it to Spotify - Komorebi `sends` Spotify from the `Center Monitor` to `Left Monitor` <= This is where you see the flash - this is where the layout probably could not update soon enough, as Spotify was added and removed very quickly. A `retile` should solve the issue - Komorebi stays on `Center Monitor` @LGUG2Z when Komorebi sends the window to another workspace it does not seem to apply workspace layout, right? So that is why the window is not resized and can "bleed through" monitors?
adam commented 2026-01-05 14:51:53 +01:00
Author
Owner
Copy Link

@Skyppex commented on GitHub (Apr 22, 2025):

I just tried running komorebic retile. It seems to just update the layout on the Left Monitor without showing Spotify itself. It just ends up looking like the screenshot i attached, but without me having to move focus to the Left Monitor workspace.

EDIT:
I focused spotify after doing the retile, it then appeared on the Center Monitor.
I then did another komorebic retile which actually moved it to the Left Monitor.

@Skyppex commented on GitHub (Apr 22, 2025): I just tried running `komorebic retile`. It seems to just update the layout on the `Left Monitor` without showing Spotify itself. It just ends up looking like the screenshot i attached, but without me having to move focus to the `Left Monitor` workspace. EDIT: I focused spotify after doing the retile, it then appeared on the `Center Monitor`. I then did another `komorebic retile` which actually moved it to the `Left Monitor`.
adam commented 2026-01-05 14:51:53 +01:00
Author
Owner
Copy Link

@CtByte commented on GitHub (Apr 22, 2025):

does it get fixed if you change focus from monitor to monitor?

EDIT:
I am not sure about the inner workings if how Komorebi manages windows, I did try to use these rules before (many of them) and I gave up as it did not work as I wanted.

I think this comes down to Windows having a closed api and this might be the best we are allowed :(

@CtByte commented on GitHub (Apr 22, 2025): does it get fixed if you change focus from monitor to monitor? EDIT: I am not sure about the inner workings if how Komorebi manages windows, I did try to use these rules before (many of them) and I gave up as it did not work as I wanted. I think this comes down to Windows having a closed api and this might be the best we are allowed :(
adam commented 2026-01-05 14:51:53 +01:00
Author
Owner
Copy Link

@Skyppex commented on GitHub (Apr 22, 2025):

does it get fixed if you change focus from monitor to monitor?

it does not. the window remain hidden, but based on some context clues (i was able to press space to play/pause music), it seems it becomes active somehow.

@Skyppex commented on GitHub (Apr 22, 2025): > does it get fixed if you change focus from monitor to monitor? it does not. the window remain hidden, but based on some context clues (i was able to press space to play/pause music), it seems it becomes active somehow.
adam commented 2026-01-05 14:51:53 +01:00
Author
Owner
Copy Link

@CtByte commented on GitHub (Apr 22, 2025):

then it might be a hidden window

try running komorebic visible-windows to see if that is a managed hidden window

https://lgug2z.github.io/komorebi/common-workflows/ignore-windows.html

@CtByte commented on GitHub (Apr 22, 2025): then it might be a hidden window try running `komorebic visible-windows` to see if that is a managed hidden window https://lgug2z.github.io/komorebi/common-workflows/ignore-windows.html
adam commented 2026-01-05 14:51:53 +01:00
Author
Owner
Copy Link

@Skyppex commented on GitHub (Apr 22, 2025):

then it might be a hidden window

try running komorebic visible-windows to see if that is a managed hidden window

Yeah, spotify appears there when it is not actually visible on my screen xD

@Skyppex commented on GitHub (Apr 22, 2025): > then it might be a hidden window > > try running `komorebic visible-windows` to see if that is a managed hidden window Yeah, spotify appears there when it is not actually visible on my screen xD
adam commented 2026-01-05 14:51:53 +01:00
Author
Owner
Copy Link

@CtByte commented on GitHub (Apr 22, 2025):

you can post the output here, I am not sure if spotify has 2 windows, one on the Center (hidden) and the other on the Left (main)

@CtByte commented on GitHub (Apr 22, 2025): you can post the output here, I am not sure if spotify has 2 windows, one on the `Center` (hidden) and the other on the `Left` (main)
adam commented 2026-01-05 14:51:53 +01:00
Author
Owner
Copy Link

@Skyppex commented on GitHub (Apr 22, 2025):

hold on, spotify just started working. I'll use wezterm-gui.exe instead.

{
  "LEN403A-4&2c4d2617&0&UID8388688": [
    {
      "title": "brage.ingebrigtsen@schibsted.com - Mozilla Thunderbird",
      "exe": "thunderbird.exe",
      "class": "MozillaWindowClass"
    },
    {
      "title": "~",
      "exe": "wezterm-gui.exe",
      "class": "org.wezfurlong.wezterm"
    }
  ],
  "PHL08F5-4&2c4d2617&0&UID41031": [
    {
      "title": "[FEAT]: Open programs on specific monitors · Issue #1418 · LGUG2Z/komorebi - Opera",
      "exe": "opera.exe",
      "class": "Chrome_WidgetWin_1"
    }
  ],
  "SAM73F7-4&2c4d2617&0&UID45383": [
    {
      "title": "~> komorebic",
      "exe": "WindowsTerminal.exe",
      "class": "CASCADIA_HOSTING_WINDOW_CLASS"
    }
  ]
}

The other here ended up being equivalent to: Left - Right - Center fyi.

@Skyppex commented on GitHub (Apr 22, 2025): hold on, spotify just started working. I'll use wezterm-gui.exe instead. ```json { "LEN403A-4&2c4d2617&0&UID8388688": [ { "title": "brage.ingebrigtsen@schibsted.com - Mozilla Thunderbird", "exe": "thunderbird.exe", "class": "MozillaWindowClass" }, { "title": "~", "exe": "wezterm-gui.exe", "class": "org.wezfurlong.wezterm" } ], "PHL08F5-4&2c4d2617&0&UID41031": [ { "title": "[FEAT]: Open programs on specific monitors · Issue #1418 · LGUG2Z/komorebi - Opera", "exe": "opera.exe", "class": "Chrome_WidgetWin_1" } ], "SAM73F7-4&2c4d2617&0&UID45383": [ { "title": "~> komorebic", "exe": "WindowsTerminal.exe", "class": "CASCADIA_HOSTING_WINDOW_CLASS" } ] } ``` The other here ended up being equivalent to: `Left` - `Right` - `Center` fyi.
adam commented 2026-01-05 14:51:53 +01:00
Author
Owner
Copy Link

@CtByte commented on GitHub (Apr 22, 2025):

and you are saying that on the Left your windows only take up half the monitor?

@CtByte commented on GitHub (Apr 22, 2025): and you are saying that on the `Left` your windows only take up half the monitor?
adam commented 2026-01-05 14:51:53 +01:00
Author
Owner
Copy Link

@Skyppex commented on GitHub (Apr 22, 2025):

and you are saying that on the Left your windows only take up half the monitor?

precisely. the other half seems to be an invisible wezterm. i can navigate to the empty space and write stuff in the prompt xD

@Skyppex commented on GitHub (Apr 22, 2025): > and you are saying that on the `Left` your windows only take up half the monitor? precisely. the other half seems to be an invisible wezterm. i can navigate to the empty space and write stuff in the prompt xD
adam commented 2026-01-05 14:51:54 +01:00
Author
Owner
Copy Link

@CtByte commented on GitHub (Apr 22, 2025):

ok, then I would say, you need an ignore rule added to your komorebi.json file

  "ignore_rules": [
    {
      "kind": "Exe",
      "id": "wezterm-gui.exe",
      "matching_strategy": "Equals"
    }
  ]
@CtByte commented on GitHub (Apr 22, 2025): ok, then I would say, you need an ignore rule added to your komorebi.json file ```json "ignore_rules": [ { "kind": "Exe", "id": "wezterm-gui.exe", "matching_strategy": "Equals" } ] ```
adam commented 2026-01-05 14:51:54 +01:00
Author
Owner
Copy Link

@Skyppex commented on GitHub (Apr 22, 2025):

well now wezterm is not managed, which i want it to be.

@Skyppex commented on GitHub (Apr 22, 2025): well now wezterm is not managed, which i want it to be.
adam commented 2026-01-05 14:51:54 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Apr 22, 2025):

Quick bit from me: Spotify's app is a PITA, there is a setting somewhere in the preferences which makes it default to starting up minimized, but it registers itself as a visible window although it is minimized. Try digging out that option and turning it off, but otherwise whenever you see a Spotify ghost tile you can alt-tab it to the foreground

@LGUG2Z commented on GitHub (Apr 22, 2025): Quick bit from me: Spotify's app is a PITA, there is a setting somewhere in the preferences which makes it default to starting up minimized, but it registers itself as a visible window although it is minimized. Try digging out that option and turning it off, but otherwise whenever you see a Spotify ghost tile you can alt-tab it to the foreground
adam commented 2026-01-05 14:51:54 +01:00
Author
Owner
Copy Link

@CtByte commented on GitHub (Apr 22, 2025):

well now wezterm is not managed, which i want it to be.

you can then make a more specific ignore rule using the Title or the Class

  "ignore_rules": [
    [
      {
        "kind": "Exe",
        "id": "wezterm-gui.exe",
        "matching_strategy": "Equals"
      },
      {
        "kind": "Title",
        "id": "~",
        "matching_strategy": "Equals"
      }
    ]
  ]
@CtByte commented on GitHub (Apr 22, 2025): > well now wezterm is not managed, which i want it to be. you can then make a more specific ignore rule using the Title or the Class ```json "ignore_rules": [ [ { "kind": "Exe", "id": "wezterm-gui.exe", "matching_strategy": "Equals" }, { "kind": "Title", "id": "~", "matching_strategy": "Equals" } ] ] ```
adam commented 2026-01-05 14:51:54 +01:00
Author
Owner
Copy Link

@Skyppex commented on GitHub (Apr 22, 2025):

this issue actually disappears when i use the "window_hiding_behaviour": "Cloak"

for me it's usually set to Minimize because then FlowLauncher can identify running apps even if komorebi hides them.
i often use FlowLauncher to change focus to an app that isn't visible on screen, therefor i never switched to Cloak since it disabled that function for me.

it will be a little annoying, but i think i can just bite the bullet here and switch to Cloak finally. there are a few other things that don't seem to work very well with Minimize

@Skyppex commented on GitHub (Apr 22, 2025): this issue actually disappears when i use the `"window_hiding_behaviour": "Cloak"` for me it's usually set to `Minimize` because then FlowLauncher can identify running apps even if komorebi hides them. i often use FlowLauncher to change focus to an app that isn't visible on screen, therefor i never switched to `Cloak` since it disabled that function for me. it will be a little annoying, but i think i can just bite the bullet here and switch to `Cloak` finally. there are a few other things that don't seem to work very well with `Minimize`
adam commented 2026-01-05 14:51:54 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Apr 22, 2025):

Let's open up an issue to track in FlowLauncher for this; Cloaked apps are part of the system and should be enumerated and identified ^

@LGUG2Z commented on GitHub (Apr 22, 2025): Let's open up an issue to track in FlowLauncher for this; Cloaked apps are part of the system and should be enumerated and identified ^
adam commented 2026-01-05 14:51:54 +01:00
Author
Owner
Copy Link

@alex-ds13 commented on GitHub (Apr 22, 2025):

@Skyppex @CtByte You don't want to add the rule to ignore wezterm. Since you actually want it to be managed. The issue is precisely that you are using Minimize as hiding behavior. The minimize hiding behavior hasn't been touched/updated in a while, so it probably has some bugs. The Cloak hiding behavior is the best one. You can however try to use Hide to see if it works better than minimize, since from my experience minimize is really slow and doesn't work very well!

@alex-ds13 commented on GitHub (Apr 22, 2025): @Skyppex @CtByte You don't want to add the rule to ignore wezterm. Since you actually want it to be managed. The issue is precisely that you are using `Minimize` as hiding behavior. The minimize hiding behavior hasn't been touched/updated in a while, so it probably has some bugs. The `Cloak` hiding behavior is the best one. You can however try to use `Hide` to see if it works better than minimize, since from my experience minimize is really slow and doesn't work very well!
adam commented 2026-01-05 14:51:54 +01:00
Author
Owner
Copy Link

@Skyppex commented on GitHub (Apr 22, 2025):

Let's open up an issue to track in FlowLauncher for this; Cloaked apps are part of the system and should be enumerated and identified ^

Its one of the old Wox plugins i think so its a lost cause, but i can check it out, see if its being maintained still :)
Closing this since its technically working now :)
Thanks for the help, all :)

@Skyppex commented on GitHub (Apr 22, 2025): > Let's open up an issue to track in FlowLauncher for this; Cloaked apps are part of the system and should be enumerated and identified ^ Its one of the old Wox plugins i think so its a lost cause, but i can check it out, see if its being maintained still :) Closing this since its technically working now :) Thanks for the help, all :)
adam commented 2026-01-05 14:51:54 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Apr 22, 2025):

Maybe @pro470 who maintains the komorebi plugin for flow launcher might be able to add something which enables identifying cloaked apps using the state? 🤔

@LGUG2Z commented on GitHub (Apr 22, 2025): Maybe @pro470 who maintains the [komorebi plugin for flow launcher](https://github.com/pro470/Flow.Launcher.Plugin.komoflow) might be able to add something which enables identifying cloaked apps using the state? 🤔
adam commented 2026-01-05 14:51:54 +01:00
Author
Owner
Copy Link

@pro470 commented on GitHub (Apr 22, 2025):

If I understand the issue correctly, it is that when you use the cloak feature, you can't switch to applications that are cloaked and not minimized with flow launcher. This is already fixed in Komoflow by using the state and the eager-focus command built in komorebi. If you do not want to use the kc keyword, just make the keyword field in the Komoflow settings blank. This allows you to just type in the executable name. I had the same issue with the minimize feature, so I implemented it in Komoflow a long time ago.

@pro470 commented on GitHub (Apr 22, 2025): If I understand the issue correctly, it is that when you use the cloak feature, you can't switch to applications that are cloaked and not minimized with flow launcher. This is already fixed in Komoflow by using the state and the eager-focus command built in komorebi. If you do not want to use the kc keyword, just make the keyword field in the Komoflow settings blank. This allows you to just type in the executable name. I had the same issue with the minimize feature, so I implemented it in Komoflow a long time ago.
adam commented 2026-01-05 14:51:54 +01:00
Author
Owner
Copy Link

@pro470 commented on GitHub (Apr 22, 2025):

It is not working for floating windows, but I can fix that for the next release. I just forgot about them when I created the feature. Maybe I should work on Komoflow when I have time, because of the new features in komorebi. I think its about time.

@pro470 commented on GitHub (Apr 22, 2025): It is not working for floating windows, but I can fix that for the next release. I just forgot about them when I created the feature. Maybe I should work on Komoflow when I have time, because of the new features in komorebi. I think its about time.
adam commented 2026-01-05 14:51:54 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Apr 22, 2025):

Thanks @pro470! If you also have time to do a little write-up that a dummy like me can follow, I can also make a YouTube video showcasing the plugin 🚀

@LGUG2Z commented on GitHub (Apr 22, 2025): Thanks @pro470! If you also have time to do a little write-up that a dummy like me can follow, I can also make a YouTube video showcasing the plugin 🚀
adam commented 2026-01-05 14:51:54 +01:00
Author
Owner
Copy Link

@Skyppex commented on GitHub (Apr 23, 2025):

The plugin for that is called Window Walker, they had an open PR for this already which was merged yesterday. Now it works for cloaked windows too :)

@Skyppex commented on GitHub (Apr 23, 2025): The plugin for that is called Window Walker, they had an open PR for this already which was merged yesterday. Now it works for cloaked windows too :)
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 enhancement
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#603
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?