FAQ¶

Does Commando run my commands for me?¶

No, not by default. It assembles the command, places it on your shell prompt, and lets you review, edit, and press Enter yourself — so cd, environment variables, and aliases keep working. Use commando search --exec if you do want it to run the command directly.

Which shells are supported?¶

The interactive summon widget supports Zsh, Bash, and Fish. The CLI itself works from any shell — it just prints the assembled command to stdout.

Is there a database?¶

No. Every piece of state is a plain TOML file you can read and edit, and shell history is read live and never copied. See Files & storage.

Does Commando slow down my shell?¶

No. It installs no preexec/precmd capture hook — only a summon widget bound to a key. History is read on demand when you open the launcher.

How is the list ordered? / How does memory rank values?¶

Both by frecency — a blend of how often and how recently you use something. The list ranks entries (bookmarks sort to the top); memory ranks remembered values per (command, variable, scope). See Argument memory.

Each whitespace-separated term is matched independently against an entry's title, description, command text, and tags, and every term must match somewhere — so deploy cluster finds a command tagged deploy whose description contains cluster, in any word order. Exact and prefix matches rank above word-prefix, contains, and subsequence ("fuzzy") matches. Matches in the title are weighted above tags, command text, and description. To restrict the list to one source, lead the query with a scope prefix (:c, :p, :h, :b) or press Tab to cycle; see Scoping to a source.

How do I keep secrets out of Commando?¶

Two independent controls: remember = "none" on a variable keeps its values out of memory.toml, and the redaction denylist hides secret-looking commands from history.

What's the difference between history and bookmarks?¶

History is everything you've run, read live and shown newest-first (capped until you search). Bookmarks are the handful you explicitly saved, with searchable tags and notes, sorted to the top.

Yes — they're plain TOML files in ~/.config/commando/cheats/. Commit them to a dotfiles repo, sync across machines, or share with your team. Every .toml in that directory is loaded.

How do I change the summon key?¶

Set key_binding in config.toml, then reload commando init zsh, bash, or fish integration.

Where does `commando add` write?¶

It appends the new cheat entry to ~/.config/commando/cheats/user.toml after validating the generated TOML.

A command has an optional flag — how do I avoid a dangling flag?¶

Put the flag inside the optional bracket with its variable: [-n <count>]. If you skip count, the whole -n <count> fragment disappears. See Template syntax.

Something looks wrong — how do I reset it?¶

Run commando state clear memory to forget parameter values, commando state clear usage to reset ranking, or commando state clear all for both. See the reset table for file-level recovery.