Guide
zsh autocomplete: the Tab menu, plugins, or a dropdown at the cursor
Last checked 17 November 2026
In short: zsh can already complete commands when you press Tab. Plugins make that faster or nicer, all inside the terminal text. Termhint takes a different route on the Mac: a native popup at the cursor that opens as you type, with descriptions for subcommands and options. Here is how the approaches differ, and what Termhint changes in your zsh setup.
Four ways to get zsh autocomplete
| Approach | When it shows | Where it shows | Cost |
|---|---|---|---|
| zsh's own completion system | When you press Tab | Below the command line, in the terminal | Built in |
| zsh-autocomplete | As you type; Tab inserts the top match, ↓ selects another | Below the command line, in the terminal | Free, MIT |
| zsh-autosuggestions | As you type | One gray suggestion after the cursor, from history or completion; → accepts it | Free, MIT |
| fzf-tab | When you press Tab | An fzf fuzzy-search menu over zsh's completions, optionally in a tmux popup | Free, MIT; needs fzf |
| Termhint | As you type | A native macOS popup at the cursor, outside the terminal text | $11.99 once, 7-day trial |
From each project's README on 17 November 2026 and the zsh manual.
The three plugins are free, open source and work in any terminal, on Linux too, and inside tmux. zsh-autocomplete asks you to remove your own compinit calls and source it near the top of .zshrc. If that covers what you need, you don't need Termhint.
zsh autocomplete vs autosuggestions
The names are close, but the tools do different jobs. zsh-autosuggestions "suggests commands as you type based on history and completions": one gray guess after the cursor that → accepts. Autocomplete, whether zsh's completion menu, the zsh-autocomplete plugin or Termhint, shows a list of the subcommands, options or files that fit where you are. One finishes a line you have likely typed before; the other shows what you can type next. More in Termhint vs zsh-autosuggestions.
What a popup at the cursor adds
- Descriptions beside every item, in an aligned column, with a colored badge for its kind (subcommand, option, file, folder, script).
- Nothing drawn in the terminal. The popup is a separate window, so your scrollback and the text below the prompt stay as they are.
- Details of the selected item below the list, or beside it when the popup is wide.
What it suggests
- Subcommands, options and arguments from Fig's open-source completion specs, plus specs generated from carapace's completers, the zsh completion functions that ship with macOS and zsh-completions.
- The scripts in your package.json after
npm run,yarn,pnpmandbun. - Your git branches, tags, remotes, stashes and aliases, ssh hosts from
~/.ssh/configandknown_hosts, Docker containers and images and Makefile targets with their##descriptions. Termhint reads them itself and never runs git, ssh, docker or make. - The command itself as you type it:
gioffersgit, from the commands on your PATH, your aliases, functions and builtins, aftersudotoo. An alias completes like what it stands for. - Files and folders where a command expects a path.
- For a command with no spec: what zsh's own completion function offers (any tool that installs one, such as Homebrew's), and if there is none, the options from its man page.
The commands, subcommands and options you use come first among equal matches. Choose what it learns from in Settings → Popup → Learn from; it keeps only their names, never your arguments.
Real output of termhint complete, the command the popup is built from (first lines shown):
$ termhint complete "git ch"
subcommand checkout Switch branches or restore working tree files
subcommand cherry-pick Apply the changes introduced by some existing commits
$ termhint complete "docker run -"
option -it Launch an interactive session
option --add-host Add a custom host-to-IP mapping (host:ip)
option -a, --attach Attach to STDIN, STDOUT or STDERR
option --cap-add Add Linux capabilities
$ termhint complete "brew ins"
subcommand install Install <formula>
Not suggested: completions you write yourself.
How Termhint hooks into zsh
- One marked block at the end of
~/.zshrc. The file is backed up first. You can turn the setup off in Settings. - Key routing. Tab, ↑, ↓, Esc and Enter go to the popup only while it is open. The rest of the time zsh gets them as usual.
- Safe if the app quits. If Termhint is not running, the keys go straight back to zsh.
- Clean removal.
termhint uninstall --allremoves the block byte for byte, along with every other change Termhint made outside the app.
Terminal, iTerm2, Ghostty, kitty, WezTerm, Alacritty and Rio need no extra permission: zsh asks the terminal where the cursor is. VS Code and its forks, Hyper, Tabby, Wave, JetBrains IDEs, Kaku, cmux, Tern and split panes in Terminal, iTerm2 and Ghostty need Accessibility to place the popup (permissions). Inside tmux it works too, in its split panes as well. If something does not show up, see troubleshooting.
How fast it is
Measured in the project: from keystroke to app, 0.11 ms at the median and 0.27 ms at the 99th percentile. termhint complete "git ch" as a separate process, including loading the 357 KB git spec, takes 10 to 20 ms wall time.
Limits
What Termhint doesn't do: autocomplete in bash or fish (bash gets the prompt themes and colors only), Linux, Intel Macs, GNU screen, or completion specs you write yourself.
Warp is not supported: its own command editor bypasses zsh's line editor (Termhint vs Warp). Setup notes for each supported app are on the terminals page; if the popup does not show, see autocomplete not working.
What it costs
Every feature works for 7 days with no account and no card. After that, a one-time license: $11.99 for 1 Mac, $19.99 for 3, $29.99 for 5, plus VAT or sales tax where it applies (pricing).