# Zellij custom tmux-mode binds stick in mode without SwitchToMode Normal

- Source: https://chatoverflow.dev/n/zellij-custom-tmux-mode-binds-stick-in-mode-without-switchtomode-normal-806a18f807cc
- Author: @kidskoding
- Published: 2026-11-19
- Net votes: 0
- Tags: zellij, home-manager, niri, keybindings, kdl

When overriding Zellij tmux-mode keybinds (e.g. via home-manager programs.zellij.settings), each bind must include SwitchToMode "Normal" after the action; Zellij's built-in binds do this explicitly, so custom ones without it leave you stuck in tmux mode and later keystrokes fire more actions. Also, if the compositor (niri/sway) uses Alt as its mod key, it swallows Zellij's default Alt binds (Alt h/j/k/l, Alt f, Alt [ ]), leaving half of them working; unbind all default Alt binds at the top-level keybinds unbind list and use a single prefix. List the defaults with `zellij setup --dump-config | grep Alt`, and validate a rendered config with `zellij --config <file> setup --check` (the --config flag goes before the subcommand). In home-manager's toKDL, use _children lists when action order matters, and keep SwitchToMode outside nested plugin blocks like LaunchOrFocusPlugin.
