###### _

_{// design by t2}

_ ![hyde_banner](Source/assets/hyde_banner.png) [![es](https://img.shields.io/badge/lang-es-yellow.svg)](Source/assets/keybinds/KEYBINDINGS.es.md) [![de](https://img.shields.io/badge/lang-de-black.svg)](Source/assets/keybinds/KEYBINDINGS.de.md) [![nl](https://img.shields.io/badge/lang-nl-green.svg)](Source/assets/keybinds/KEYBINDINGS.nl.md) [![中文](https://img.shields.io/badge/lang-中文-orange.svg)](Source/assets/keybinds/KEYBINDINGS.zh.md) [![fr](https://img.shields.io/badge/lang-fr-blue.svg)](Source/assets/keybinds/KEYBINDINGS.fr.md) [![ar](https://img.shields.io/badge/lang-AR-orange.svg)](Source/assets/keybinds/KEYBINDINGS.ar.md) [![pt-br](https://img.shields.io/badge/lang-pt--br-brightgreen.svg)](Source/assets/keybinds/KEYBINDINGS.pt-br.md)

Window Management Misc Launcher Hardware Controls Utilities Theming and Wallpaper Workspaces

Here are all HyDE specific keybindings listed. > [!TIP] > Super + / shows the keybindings. ##

Your own keybindings go in: ```bash ~/.config/hypr/hyprland.lua ``` That file is yours — updates never overwrite it. HyDE's own binds live in `~/.local/share/hypr/lua/key_binds.lua`, which **is** overwritten on every update, so edits there are lost. Your file loads after HyDE's binds, which is why anything you write there wins. The one thing loaded after it is your selected workflow, which can override compositor settings. For example, to bind the **HyDE Game Launcher** to SUPER + Space: ```lua hl.bind("SUPER + SPACE", hl.dsp.exec_cmd(hyde.sh.gamelauncher()), { description = "[Utilities] game launcher", }) ``` Add a `description` in the `[Group|Subgroup] text` shape and your bind shows up in the keybinding hint under that group. Without one it appears as a raw dispatcher call under "Misc". `hyde.sh.()` builds a `hyde-shell` command — here `hyde-shell gamelauncher`, the same thing you can run from a terminal. Some names are shortcuts for something longer: `hyde.sh.screenshot.snip()` is `hyde-shell screenshot s`, `hyde.sh.menu.binds()` is `hyde-shell keybinds_hint`. The full list is `hyde.command_map` in `~/.local/share/hypr/lua/hyde/dispatcher.lua`. ### Rebinding something HyDE already uses Bind the same combination again and yours replaces it — but **copy the flags too**. A bind counts as the same one only when its flags match, and `description` is not a flag. Thirty-three of HyDE's binds carry one: | Flags | Binds | | :--------------------------------------------- | :--------------------------------------------------------------------------------------- | | `locked` | media keys, mute, keyboard layout, game mode, and every screen-capture bind | | `locked` and `repeating` | volume up and down, brightness up and down — on both the function row and the media keys | | `repeating` | resize active window, move active window | | `transparent`, and `release` on the apply step | the alt-tab switcher | Miss one and you end up with **both** binds firing on that combination. So to move the mute key from F10 to F9, carry `locked` across: ```lua hl.unbind("F10") hl.bind("F9", hl.dsp.exec_cmd(hyde.sh.volumecontrol("-o", "m")), { locked = true, description = "[Hardware Controls|Audio] un/mute output", }) ``` `hl.unbind` takes the combination exactly as the bind was registered, with single spaces around each `+`. Copy the spelling from `key_binds.lua` rather than guessing: several binds are written there with `CONTROL` where you might expect `CTRL`. Rebinding is the safer route — HyDE replaces the old bind for you, so you never have to match a string. ### Seeing your live keybindings SUPER + / reads the binds from the compositor itself, so it shows your own alongside HyDE's and reflects whatever replaced a default. This table describes the shipped defaults only. The list is cached, and the cache is refreshed when you close it — so right after adding a bind, the first press may still show the previous list. Press it twice, or run `hyde-shell keybinds_hint --reload`.

🡅

_{Last edited on: 30/07/2026}