What problem does it solve?
WezTerm users need a reliable way to plan, write, and validate their terminal multiplexer and keybinding setup without guessing at config placement or reload behavior.
Core Features & Use Cases
- Lua config authoring and placement: Covers where WezTerm looks for
~/.wezterm.lua vs $XDG_CONFIG_HOME and how to override discovery with CLI flags or WEZTERM_CONFIG_FILE.
- Multiplexer workflows (SSH/WSL/domains, workspaces): Supports domain-aware pane/window actions and workspace switching for recurring environments.
- Operational ergonomics (key bindings and UI behavior): Provides common configuration patterns for appearance, copy mode, launcher prompts, and pane/tab/window actions you can directly encode in Lua.
Quick Start
Write your WezTerm setup into ~/.wezterm.lua, then run wezterm start using your intended config discovery path so your custom key bindings, tabs/panes, and appearance take effect immediately.