Termhint Get Termhint

Where Termhint's completions come from

Updated 19 November 2026All docs

Termhint completes a command from the first source that has it: a bundled completion spec, then zsh's own completion function, then the command's man page. Live values such as git branches and ssh hosts fill in the arguments. This page lists each source in that order and how many commands they cover.

The order Termhint uses

For each command line, Termhint takes the command (an alias as its expansion) and looks for:

  1. A bundled spec for the command, or for the command it is another name of.
  2. zsh's own completion for the command, when there is no spec.
  3. The man page's options, when zsh has no completion function for it either.

Inside a spec, arguments can also come from live values, files and folders, or zsh (below). The command word itself comes from your shell: see What it completes.

Bundled specs

A spec describes a command's subcommands, options and arguments. Termhint ships them inside the app and reads them locally; nothing is downloaded while you type.

Source What it adds License
Fig's completion specs 1,475 spec files from the open-source @withfig/autocomplete package MIT
Termhint's own The spec for termhint itself
carapace-bin 481 commands Fig's specs lack MIT
macOS's zsh completion functions 1,075 commands zsh license
zsh-completions 180 commands zsh license
A command's own --help 72 reviewed tools nothing else completes (warp-cli, devicectl, fastboot, jshell, x265, …)

Fig's specs come first. The generated specs (the last four rows) are made before release, only for commands that no earlier source completes, in a sandbox with no network. No GPL-licensed source is used. Termhint never runs a tool's --help on your Mac.

Termhint supports the Fig spec format and is not affiliated with Fig or AWS.

Other names of a command

A command installed under a versioned or second name uses the spec of that command: pip3.14 uses pip3, gawk-5.4.1 uses gawk, cpan5.34 uses cpan, and yarnpkg, bundler, pn/pnx, zstdmt and kubectl.docker use theirs. A name that only ends in digits, such as x264 or base64, is its own command.

Values that differ per Mac

Where a generated spec takes values that depend on the Mac (processes, users, hosts), Termhint asks your zsh for them as you type.

What specs cannot do yet

Termhint reads specs as data. It does not run a spec's JavaScript, and of Fig's generators it handles only the ones it reads itself (live values, below). Values such as kubectl resources or tmux sessions are not suggested. Fig's history template is not used: Termhint does not suggest lines from your shell history.

zsh's own completions

For a command without a spec, Termhint asks your zsh what Tab would offer, with the descriptions, and filters the answer as you type. This covers any tool that installs a zsh completion function, such as the functions in Homebrew's site-functions folder.

Man pages

When zsh has no completion function for a command, Termhint reads the options from its man page. The page is rendered with macOS's /usr/bin/mandoc and cached until the page changes.

termhint complete cannot ask zsh, so for a command without a spec it always shows the man page's options (see Test completions).

Live values

Termhint reads these values itself, without starting git, ssh, make or docker. Each file is read again only when its size, time or inode changed; only regular files are read, up to a size limit.

Values Read from More
package.json scripts for npm run, yarn, pnpm, bun, nr and rushx The nearest package.json above the shell's folder, in file order, with the script's command as the description
git branches (newest first, the current one marked), remote branches, tags, remotes, stashes and git aliases The repository's own files (worktrees followed). Credentials are cut from remote URLs; stashes show their message only Git autocomplete
ssh hosts ~/.ssh/config (with Include, without wildcard patterns) and the plain host names in known_hosts. A user@ you typed is kept SSH autocomplete
Makefile targets GNUmakefile, makefile or Makefile in the folder, with include followed one level. The description is the ## help comment or the comment above the target; a ##@ Section comment is shown in front. Targets marked [prod], [production], [danger] or [caution] show in red Makefile autocomplete
Docker containers (running or all) and images The Docker engine's own Unix socket of the current docker context (unix:// only, owned by you or root). Cached and refreshed in the background, so a keystroke never waits; the popup updates when they change Docker autocomplete

After a script name for npm run and the others, the words belong to the script, so nothing is suggested there.

Files and folders

Where a spec takes a file or a folder, Termhint lists the folder you typed (src/, ~/, /usr/), else the shell's current folder. cd gets folders only; a spec can put certain file types first (tsc lists .ts files first).

Coverage

With all bundled specs, Termhint completes 3,272 commands. Measured on 18 November 2026:

Measured against Covered
tldr-pages' common and macOS pages 1,866 of 5,105 (37%)
Homebrew's executables 1,387 of 22,310 (6.2%)

Commands without a spec still get zsh's own completions or their man page's options. The menu-bar panel shows the number of commands with a bundled spec; its help counts the commands on your Mac's PATH that get completions (a spec, a zsh function or a man page with options), from the latest terminal tab.

Your own completions

There is no folder for your own specs. For a command Termhint has no spec for, install a zsh completion function for it (on your fpath, loaded by compinit): Termhint uses what zsh's Tab offers.