[BUG]: Komorebi not managing Visual Studio Code after installing the "Vibrancy Continued" extension. #671

New Issue

2026-01-05T14:52:20+01:00

adam commented

2026-01-05 14:52:20 +01:00

Originally created by @santiagoavs on GitHub (Sep 1, 2025).

Summary

I installed the Vibrancy Continued extension on Visual Studio Code 1.103.2, and when I ran the command for the application of Vibrancy (>Reload Vibrancy) and reloaded vscode, suddenly Komorebi stopped managing it. I know why the "Your Code installation appears to be corrupt" advertise shows up, Vibrancy modifies some code that visual studio reads as corrupt, but I don't know if this makes some trouble with Komorebi. In the configuration of Komorebi I didn't have any rule at all, so I made one to see if Komorebi could recognize the vscode window with that, but it didn't work. I made the rule after looking at the window information with Spy++ so I could get the window class right. How could I solve this?

Version Information

The version of Windows I'm using is Windows 11 Home, the version is: 10.0.26100 N/A Build 26100
Visual Studio Code version and some more information:
Version: 1.103.2 (user setup)
Commit: 6f17636121051a53c88d3e605c491d22af2ba755
Date: 2025-08-20T16:45:34.255Z
Electron: 37.2.3
ElectronBuildId: 12035395
Chromium: 138.0.7204.100
Node.js: 22.17.0
V8: 13.8.500258-electron.0
OS: Windows_NT x64 10.0.26100
Komorebi version:
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.25/schema.json",
  "app_specific_configuration_path": "$Env:USERPROFILE/.komorebi/applications.yaml",
  "window_hiding_behaviour": "Cloak",
  "focus_follows_mouse": "Windows",
  "cross_monitor_move_behaviour": "Insert",
  "default_workspace_padding": 5,
  "default_container_padding": 5,
  "border": true,
  "border_width": 2,
  "border_offset": -1,
  "border_colours": {
    "single": "#4e88d9",
    "stack": "#4e88d9",
    "monocle": "#4e88d9",
    "unfocused": "#808080"
  },
  "rules": [
       {
         "window_class": "Chrome_WidgetWin_1",
          "window_title_contains": "Visual Studio Code",
          "manage_as": "tiling"
       }
     ],
  "stackbar": {
    "height": 30,
    "mode": "OnStack",
    "tabs": {
      "width": 300,
      "focused_text": "#4e88d9",
      "unfocused_text": "#b3b3b3",
      "background": "#303949"
    }
  },
  "monitors": [
    {
      "workspaces": [
        {
          "name": "I",
          "layout": "BSP"
        },
        {
          "name": "II",
          "layout": "VerticalStack"
        },
        {
          "name": "III",
          "layout": "HorizontalStack"
        },
        {
          "name": "IV",
          "layout": "UltrawideVerticalStack"
        },
        {
          "name": "V",
          "layout": "Rows"
        }
      ]
    }
  ]
}

Hotkey Configuration

This is my komorebi.ahk configuration in a txt

komorebi-ahk.txt

Output of komorebic check

KOMOREBI_CONFIG_HOME detected: C:\Users\santi.komorebi

Looking for configuration files in C:\Users\santi.komorebi

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

Your configuration file contains some options that have been renamed or deprecated:

"applications.yaml" is now "applications.json"

"focus_follows_mouse" is now end-of-life

End-of-life features will not receive any further bug fixes or updates; they should not be used

Found C:\Users\santi.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 @santiagoavs on GitHub (Sep 1, 2025). ### Summary I installed the Vibrancy Continued extension on Visual Studio Code 1.103.2, and when I ran the command for the application of Vibrancy (>Reload Vibrancy) and reloaded vscode, suddenly Komorebi stopped managing it. I know why the "Your Code installation appears to be corrupt" advertise shows up, Vibrancy modifies some code that visual studio reads as corrupt, but I don't know if this makes some trouble with Komorebi. In the configuration of Komorebi I didn't have any rule at all, so I made one to see if Komorebi could recognize the vscode window with that, but it didn't work. I made the rule after looking at the window information with Spy++ so I could get the window class right. How could I solve this? <img width="1918" height="1078" alt="Image" src="https://github.com/user-attachments/assets/1633705a-1094-4588-a9d2-2a6b03365137" /> <img width="1919" height="1079" alt="Image" src="https://github.com/user-attachments/assets/212505e3-b5e7-4b6a-bd70-62b5ce2dd563" /> ### Version Information The version of Windows I'm using is Windows 11 Home, the version is: 10.0.26100 N/A Build 26100 Visual Studio Code version and some more information: Version: 1.103.2 (user setup) Commit: 6f17636121051a53c88d3e605c491d22af2ba755 Date: 2025-08-20T16:45:34.255Z Electron: 37.2.3 ElectronBuildId: 12035395 Chromium: 138.0.7204.100 Node.js: 22.17.0 V8: 13.8.500258-electron.0 OS: Windows_NT x64 10.0.26100 Komorebi version: 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.25/schema.json", "app_specific_configuration_path": "$Env:USERPROFILE/.komorebi/applications.yaml", "window_hiding_behaviour": "Cloak", "focus_follows_mouse": "Windows", "cross_monitor_move_behaviour": "Insert", "default_workspace_padding": 5, "default_container_padding": 5, "border": true, "border_width": 2, "border_offset": -1, "border_colours": { "single": "#4e88d9", "stack": "#4e88d9", "monocle": "#4e88d9", "unfocused": "#808080" }, "rules": [ { "window_class": "Chrome_WidgetWin_1", "window_title_contains": "Visual Studio Code", "manage_as": "tiling" } ], "stackbar": { "height": 30, "mode": "OnStack", "tabs": { "width": 300, "focused_text": "#4e88d9", "unfocused_text": "#b3b3b3", "background": "#303949" } }, "monitors": [ { "workspaces": [ { "name": "I", "layout": "BSP" }, { "name": "II", "layout": "VerticalStack" }, { "name": "III", "layout": "HorizontalStack" }, { "name": "IV", "layout": "UltrawideVerticalStack" }, { "name": "V", "layout": "Rows" } ] } ] } ``` ### Hotkey Configuration This is my komorebi.ahk configuration in a txt [komorebi-ahk.txt](https://github.com/user-attachments/files/22071074/komorebi-ahk.txt) ### Output of komorebic check KOMOREBI_CONFIG_HOME detected: C:\Users\santi\.komorebi Looking for configuration files in C:\Users\santi\.komorebi Found komorebi.json; this file can be passed to the start command with the --config flag Your configuration file contains some options that have been renamed or deprecated: "applications.yaml" is now "applications.json" "focus_follows_mouse" is now end-of-life End-of-life features will not receive any further bug fixes or updates; they should not be used Found C:\Users\santi\.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:20 +01:00

adam closed this issue

2026-01-05 14:52:20 +01:00

adam commented

2026-01-05 14:52:20 +01:00

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

If this VSCode mod changes the transparency attributes of the window, it will not be managed; komorebi only supports modifying the transparency of windows through the window manager, not through configuration options or extensions in applications themselves.

@LGUG2Z commented on GitHub (Sep 2, 2025): If this VSCode mod changes the transparency attributes of the window, it will not be managed; komorebi only supports modifying the transparency of windows through the window manager, not through configuration options or extensions in applications themselves.

adam commented

2026-01-05 14:52:20 +01:00

@santiagoavs commented on GitHub (Sep 5, 2025):

Thanks for the acclaration.

@santiagoavs commented on GitHub (Sep 5, 2025): Thanks for the acclaration.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/komorebi#671