Skip to content

mxr keys

Generated from mxr keys --help. After editing crates/daemon/src/cli/, update and review the snapshots with scripts/cargo-test -p mxr --test cli_help, then rebuild site/.

Every keyboard shortcut in the TUI and the web app, from one definition

mxr keys [OPTIONS] [COMMAND]
Subcommand Purpose
explain What a key does, in each client; with –context, what it does there
check Check keys.toml and name everything mxr would ignore in it
help Print this message or the help of the given subcommand(s)
Flag Description
--client <CLIENT> Only this client’s keys [possible values: tui, web]
--context <CONTEXT> Only keys live in this place: a TUI context or web scope, such as todo
--format <FORMAT> [possible values: table, json, jsonl, csv, ids]
-h, --help Print help

List every keyboard shortcut in the TUI and the web app from mxr’s one key definition, or ask what a key does in a place. See keybindings.

Terminal window
mxr keys --client tui --context list
mxr keys explain e --context todo
mxr keys check
mxr keys --client web --format json

Check keys.toml and name everything mxr would ignore in it

mxr keys check [OPTIONS] [FILE]
Flag Description
[FILE] The file to check; defaults to keys.toml beside your config
Flag Description
--client <CLIENT> Only this client’s keys [possible values: tui, web]
--context <CONTEXT> Only keys live in this place: a TUI context or web scope, such as todo
--format <FORMAT> [possible values: table, json, jsonl, csv, ids]
-h, --help Print help

What a key does, in each client; with –context, what it does there

mxr keys explain [OPTIONS] <KEY>
Flag Description
<KEY> The key as mxr spells it, such as e, g i or Mod+k
Flag Description
--client <CLIENT> Only this client’s keys [possible values: tui, web]
--context <CONTEXT> Only keys live in this place: a TUI context or web scope, such as todo
--format <FORMAT> [possible values: table, json, jsonl, csv, ids]
-h, --help Print help