Terminals · tmux
tmux autocomplete: a zsh popup in every tmux pane
Last checked 19 November 2026
In short: Termhint's zsh autocomplete popup works inside tmux, in tmux's own split panes too, in the terminals Termhint supports. Nothing to add to .tmux.conf. GNU screen is not supported.
Set up autocomplete in tmux
- Download Termhint, move it to Applications and open it. On launch it adds one marked block to
~/.zshrc, backed up first. - If your terminal needs Accessibility (VS Code and its forks, JetBrains IDEs and the others in the terminals table), allow it. tmux doesn't change that.
- Start a new tmux session, or a new window or pane in a running one, so its zsh loads the block.
tmuxmust be on the PATH of the shell. - Split a pane and type
git push origin. The popup opens at the cursor in that pane with your branches, such asmainandfeature/login.
How Termhint follows tmux's panes
On every edit zsh asks for the pane's cursor cell, and zsh also asks tmux where the pane sits in the window: one tmux display after a resize, at most every five seconds. That is why tmux must be on the shell's PATH. From the two, Termhint knows where the cursor is in the whole terminal window and places the popup there. This is why tmux's split panes work even in terminals whose own splits don't, such as kitty.
Where it works
- Terminal and iTerm2, without Accessibility.
- Ghostty, kitty, WezTerm, Alacritty and Rio, without Accessibility.
- VS Code and its forks, JetBrains IDEs and the others that need Accessibility, with it.
What works inside tmux
- The popup with completions for 3,272 commands, the command names on your PATH, git branches, ssh hosts, Docker containers and Makefile targets.
- Prompt themes, drawn by the shell.
- Not inside tmux: terminal colors and tab titles. Termhint does not complete tmux's session names yet.
Not working?
- Panes started before Termhint set up zsh don't have it; open a new pane or window.
- Check
tmuxis on the PATH inside the pane:command -v tmux. - In a terminal that needs Accessibility, check it is allowed.
- Not inside GNU screen, or screen inside tmux.
More fixes: terminal autocomplete not working and troubleshooting.
FAQ
Does Termhint work inside tmux?
Yes, in any supported terminal, and in tmux's own split panes too. tmux must be on the PATH of the shell.
Does tmux need the Accessibility permission?
tmux changes nothing about it: in a terminal that needs Accessibility, such as VS Code, it is still needed; in Ghostty, kitty or WezTerm it is not.
Do terminal colors and tab titles work inside tmux?
Not inside tmux. Set them outside tmux; the popup and prompt themes work inside it.
What about GNU screen?
GNU screen is not supported.