Command Palette

Open the command palette with SUPER+SHIFT+P (Command+Shift+P on macOS) or CTRL+SHIFT+P. Type to search, use the arrow keys to select a result, and press Enter to run it. The Actions & Tasks menu includes your configured Nash tasks.

Commands you use come first

Nash 0.9.4 ranks commands and tasks by how often and how recently you use them. When the search is empty, your frequently and recently used entries rise to the top.

Searching still prioritizes the text match:

  1. An exact title.
  2. A title that starts with your search.
  3. A word in the title that starts with it.
  4. Another fuzzy match in the title.
  5. A word in the description that starts with it.
  6. Another match in the description.

Among equally good matches, usage determines the order. A frequently used command does not displace a stronger kind of text match.

Shortcuts and customization

Since Nash 0.10.0, shortcut labels reflect the live bindings, including custom Lua bindings and RunCommand aliases, rather than just bundled keys. Inspect your bindings with nash show-keys --lua.

Customize commands and shortcuts by ID in commands.toml; use nash config defaults commands.toml to find the bundled entries. See Commands and tasks for examples, hiding entries, and project overrides.

Local usage history

Commands are tracked by their id in commands.toml and tasks by their id in tasks.toml. Renaming a title keeps its history; changing its ID starts a new history. Tasks with the same ID share history across projects.

Nash stores usage in:

~/.config/nash/state/palette-usage.json

The history records command and task usage, not terminal input or output. It never leaves your machine. To reset the ranking history, close Nash and delete that file. This does not delete your commands or tasks.

Related pages