Supported terminals for Termhint autocomplete
Updated 19 November 2026All docs
Termhint's autocomplete popup works with zsh in 22 Mac terminal apps and editors, and inside tmux in any of them. This page lists which ones need the Accessibility permission, where split panes work, and what to set up in each. Warp and GNU screen are not supported.
Supported terminals at a glance
| Terminal | Accessibility | Split panes | Notes |
|---|---|---|---|
| Terminal (Terminal.app) | Not needed | With Accessibility | A custom margin setting can shift the popup a little without Accessibility |
| iTerm2 | Not needed | With Accessibility | |
| Ghostty | Not needed | With Accessibility | Custom window padding or tab bar settings can shift the popup a little |
| WezTerm | Not needed | Yes | Custom window padding or tab bar settings can shift the popup a little |
| kitty | Not needed | No: only a pane that fills the window | tmux's split panes work |
| Rio | Not needed | No: only a pane that fills the window | tmux's split panes work |
| Alacritty | Not needed | Has no split panes | Its layout is not yet tested |
| Kaku | Needed | Yes | |
| cmux | Needed | Yes | Its sidebar is fine |
| Tern | Needed | Yes | The popup can sit one cell left of the word |
| VS Code (Insiders too), VSCodium | Needed | Set editor.accessibilitySupport to off |
|
| Cursor, Windsurf | Needed | As VS Code | |
| Kiro, Trae, Positron | Needed | As VS Code | |
| Hyper, Tabby, Wave | Needed | As VS Code | |
| JetBrains IDEs: IntelliJ IDEA, PyCharm, WebStorm, GoLand, CLion, Rider, RubyMine, PhpStorm, DataGrip, RustRover | Needed | The Terminal tool window; the popup can sit one cell left of the word | |
| Zed (Zed Preview too) | Not needed | Off until you turn on Autocomplete in Zed | |
| tmux, in any of the above | As the terminal it runs in | Yes, tmux's own panes | tmux must be on the shell's PATH |
| Warp | Not supported | ||
| GNU screen | Not supported | ||
| Any other app | Tried first | Termhint tries Accessibility, then the cursor cell |
In Termhint, Settings → Terminal → Apps → Every supported terminal shows these apps with a check for the ones on your Mac. Point at one to see how Termhint finds its cursor there. An overview for each terminal is on Terminals.
Each terminal needs zsh and a tab opened after Termhint set up ~/.zshrc. For the permission itself, see Permissions.
How Termhint finds the cursor
The popup opens under the text cursor, and terminals tell macOS where it is in different ways:
- zsh asks the terminal. In Terminal, iTerm2, Ghostty, kitty, WezTerm, Alacritty and Rio, zsh asks the terminal for the cursor cell and the cell size on every edit, with standard queries that print nothing (about a millisecond; keys typed meanwhile are kept). Termhint places the popup in the window by the terminal's default layout. The window's frame is public, so no permission is needed.
- Accessibility. Kaku and JetBrains IDEs show the cursor in their accessibility text. In VS Code and the other Electron apps (its forks, Hyper, Tabby, Wave), Termhint turns on the app's accessibility tree and reads the cursor from it. cmux and Tern combine Accessibility with the cursor cell zsh asks for.
- An input method. Zed's terminal is in no accessibility tree, so a hidden input method of Termhint's tells it where Zed's cursor is.
A split pane also needs to know where the pane sits in the window. Terminal, iTerm2 and Ghostty report it through Accessibility, WezTerm through wezterm cli list, and tmux through tmux display. kitty and Rio don't report it.
Termhint never needs Screen Recording.
Terminal and iTerm2
Without Accessibility, zsh asks the terminal where the cursor is and the popup works in a window that is not split. For split panes, allow Termhint in System Settings → Privacy & Security → Accessibility. With Accessibility, Termhint reads the cursor from the terminal directly.
Ghostty
A single pane needs no permission. In split panes, allow Accessibility: macOS then reports the view of the focused pane. Without it, the popup shows only in a pane that fills the window.
WezTerm
No permission, split panes included. For a split pane, Termhint runs WezTerm's own wezterm cli list to learn where the pane starts, again only after a resize or after two seconds. Kaku, a WezTerm fork, works through Accessibility instead (split panes too).
kitty and Rio
No permission. kitty and Rio report the cursor inside a pane but not where the pane sits in the window, so the popup shows only in a window or pane that fills the window. For split panes, run tmux inside them: tmux tells Termhint where each of its panes sits.
Alacritty
No permission. Alacritty has no split panes. Its window layout is not yet tested, so the popup can be placed a little off.
VS Code and its forks
VS Code (Insiders too), VSCodium, Cursor, Windsurf, Kiro, Trae and Positron need Accessibility: Termhint turns on Electron's accessibility tree in the editor to find the terminal cursor.
- Allow Termhint in System Settings → Privacy & Security → Accessibility.
- In the editor's
settings.json, set"editor.accessibilitySupport": "off", so the editor does not switch to screen-reader mode. - Turn off the editor's own terminal suggestions, or you get two popups. In VS Code that is
"terminal.integrated.suggest.enabled": false.
Hyper, Tabby and Wave are Electron apps too and need Accessibility the same way.
JetBrains IDEs
IntelliJ IDEA, PyCharm, WebStorm, GoLand, CLion, Rider, RubyMine, PhpStorm, DataGrip and RustRover: the popup works in the Terminal tool window. They need Accessibility; their accessibility text gives the cursor. The popup can sit one cell left of the word, when Termhint reads the cursor before the terminal has caught up.
Kaku, cmux and Tern
All three need Accessibility, and split panes work in each.
- Kaku: its accessibility text gives the cursor.
- cmux: zsh asks for the cursor cell, and Accessibility gives the terminal view right of its sidebar.
- Tern: Accessibility gives the cursor's place, zsh asks for the cell width. The popup can sit one cell left of the word.
Zed
Autocomplete in Zed (and Zed Preview) is off by default. Turn it on in Settings → Terminal → Apps → Autocomplete in Zed, or:
termhint settings set terminals.zed-input on
Zed's terminal is in no accessibility tree, so Termhint links a hidden input method from inside Termhint.app into ~/Library/Input Methods and selects it. It is hidden from the input menu and leaves your keyboard layout as it is. It passes every key on, never reads what you type, and tells Termhint only where Zed's text cursor is. No Accessibility is needed for Zed.
- Termhint links the input method again at launch after an update or a move. If the popup does not show, turn the switch off and on.
- To remove it: turn the switch off, or
termhint settings set terminals.zed-input off.termhint uninstall --allremoves it too. By hand: delete~/Library/Input Methods/TermhintInput.appand log out.
tmux
The popup works inside tmux in any supported terminal, in tmux's own split panes too. Nothing goes in .tmux.conf.
tmuxmust be on the shell'sPATH(command -v tmuxprints it).- Start a new session, window or pane after Termhint set up
~/.zshrc, so its zsh loads the block. - zsh asks the terminal for the cursor in the pane, and
tmux displaytells where the pane sits (once after a resize, at most every five seconds). - In a terminal that needs Accessibility (VS Code, JetBrains IDEs, …) it is still needed; tmux changes nothing about that.
- Terminal colors and tab titles are not set inside tmux; the popup and prompt themes work.
GNU screen
Not supported. Inside screen, zsh does not ask the terminal for the cursor, and colors and tab titles don't work. Use tmux instead.
Warp
Not supported. Typing in Warp goes to its own command editor instead of zsh's line editor, where Termhint's popup works. Termhint vs Warp compares the two.
Other apps
An app not in the table is tried with Accessibility first, then its Electron accessibility tree, then the cursor cell zsh asks for.
If the popup does not show in your terminal, see Autocomplete not working.