> For the complete documentation index, see [llms.txt](https://kaizo-1.gitbook.io/kaizo-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kaizo-1.gitbook.io/kaizo-docs/installation/desktops-and-window-managers.md).

# Desktops and window managers

Kaizo works on every window manager.

That includes normal desktops and tiling compositors. The overlay follows the Sober window, and click-through works.

## Works on

These are all fine:

* KDE Plasma
* GNOME
* Cinnamon
* XFCE
* Hyprland
* niri
* Sway
* river
* i3
* bspwm
* AwesomeWM
* dwm
* Qtile
* other stacking or tiling setups like that

On these, the overlay should sit over Sober like it should.

## Put Sober on XWayland

Sober must run as XWayland, not native Wayland. Do this once, then fully restart Sober.

```bash
flatpak override --user --socket=x11 --nosocket=wayland org.vinegarhq.Sober
```

Then quit Sober completely and open it again. If you skip the restart, Kaizo cannot track the game window.

You can do the same in Flatseal: open Sober, enable X11, and disable Wayland.

{% hint style="warning" %}
Do this before you launch Kaizo. A Sober that is already open will stay on Wayland until you restart it.
{% endhint %}

## Overlay

By default the overlay follows the Sober window. You can move the game and the overlay stays on it.

In the menu, go to **Settings → Displays → Overlay Monitor**:

* **Auto (follow game)** follows the Sober window
* A named monitor fills that whole display

{% hint style="warning" %}
**KDE overlay is all black?** In System Settings, turn off **Allow applications to block compositing** under **Display & Monitor → Compositor**. See Common issues.
{% endhint %}

## Related

* Requirements
* Common issues
* How to run
* Installation


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kaizo-1.gitbook.io/kaizo-docs/installation/desktops-and-window-managers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.