Docs
Why does terminal autocomplete need Accessibility permission?
Updated 19 November 2026
In short: to open the popup right under your cursor, Termhint has to know where the cursor is. In editor terminals, JetBrains IDEs, Kaku, cmux, Tern and split panes of Terminal, iTerm2 and Ghostty it reads that from the other app's window through macOS's accessibility API, so those need the Accessibility permission. Terminal, iTerm2, Ghostty, kitty, WezTerm, Alacritty and Rio windows don't: there zsh asks the terminal for the cursor cell. Below is every permission Termhint can ask for, what uses it, what works without it, and how to give it and take it back.
Accessibility
What uses it. Finding the text cursor in another app's window, so the popup opens right under it:
- Terminal and iTerm2: macOS's accessibility API gives the cursor's position when it is allowed, and is needed for their split panes. Without it, zsh asks the terminal where the cursor is.
- VS Code, VS Code Insiders, VSCodium, Cursor, Windsurf, Kiro, Trae, Positron, Hyper, Tabby and Wave: Termhint turns on Electron's accessibility tree in that app and reads the cursor from it. Set
"editor.accessibilitySupport": "off"in VS Code or Cursor so the editor does not switch to screen-reader mode. - Kaku, JetBrains IDEs, cmux and Tern: their accessibility text or terminal view gives the cursor's place.
- Ghostty's split panes: macOS reports the focused pane.
What works without it.
- The popup in Terminal, iTerm2, Ghostty, kitty, WezTerm, Alacritty and Rio windows (WezTerm's split panes too), and in tmux inside them: zsh asks the terminal for the cursor cell, and the app places the popup in the window, whose frame is public.
- Zed, once you turn on Settings → Terminal → Apps → Autocomplete in Zed: a hidden input method tells Termhint where the cursor is; it passes every key on and never reads what you type.
- Prompt themes, terminal colors, the tab title, runtimes and every
termhintcommand. - Demo mode:
open -n /Applications/Termhint.app --args --demo.
Termhint does not need Screen Recording: window positions and sizes need no permission. Programs Termhint starts (the runtime helper, brew, a login shell, package installs) run as their own responsible process, so they cannot use Termhint's Accessibility permission.
Grant. On its first launch Termhint shows macOS's prompt. Later, use Allow in Settings or in the panel under the menu-bar icon, or go to System Settings → Privacy & Security → Accessibility and turn on Termhint. The app notices the change without a restart. termhint settings get app.accessibility answers granted or not granted.
Revoke. Turn Termhint off in System Settings → Privacy & Security → Accessibility, or remove it from the list with −. From a terminal:
tccutil reset Accessibility dev.termhint.Termhint
Moving the app to the Trash does not remove the entry; remove it there. If the panel still asks after you allowed it, see troubleshooting.
Open at login
What uses it. Termhint as a login item, so autocomplete runs after you log in. Off by default.
Without it. Everything works once you open Termhint yourself. Commands that need the app open it in the background.
Grant. Settings → App, the menu-bar panel, or termhint settings set app.open-at-login on. If the state shows "needs approval", allow Termhint in System Settings → General → Login Items.
Revoke. The same switch, termhint settings set app.open-at-login off, or System Settings → General → Login Items.
Administrator helper (Login Items approval)
What uses it. An optional helper that runs as root, turned on in Settings → Runtimes → Xcode → Administrator helper. With it, two Xcode steps run without a password: Make Default (xcode-select -s) and Finish Setup (Xcode's license and first launch). It talks only to Termhint.app, and each end checks the other's code signature. It accepts only an Xcode directly in /Applications, offers no other commands, and quits a minute after its last request.
Without it. The same two steps ask for your administrator password each time. Nothing else uses the helper.
Grant. Turn it on in Settings → Runtimes → Xcode. macOS then wants it approved: Termhint opens System Settings → General → Login Items, where you allow it.
Revoke. Turn it off in Settings → Runtimes → Xcode, or in System Settings → General → Login Items.
Administrator password
Asked only by the two Xcode steps above, when the administrator helper is off:
termhint xcode select <version>/ Make Default:xcode-select -s.termhint xcode first-launch <version>/ Finish Setup: the Xcode license and first launch. The app is moved into a fresh root-only folder, its Apple signature checked again there, Xcode's first launch run, and the app moved back.
From a terminal the prompt is sudo's; from the app it is macOS's administrator dialog. Each step asks once. More on Xcode versions: Termhint and xcodes.
Keychain
Termhint keeps its license record and, if you sign in for Xcode downloads, your Apple developer session in the login keychain (privacy policy). Termhint.app reads its license item without asking; macOS asks if another program wants it. These items stay when the app is deleted.
Files and folders
Termhint asks for no Files and Folders or Full Disk Access permission. The app reads the folder being typed (to list files) and the nearest package.json. If a shell is in a folder macOS protects, such as Desktop, Documents or Downloads, macOS may ask whether Termhint may access it. Without that access the popup lists no files there; everything else works.
Not used
- Automation (Apple events). Termhint does not control other apps. The iTerm2 font setting that
termhint icons on iterm2changes is written to iTerm2's preferences while iTerm2 is not running, not by scripting the app. - App Management. Termhint does not ask for it. An Xcode that an older Termhint left owned by root cannot be moved to the Trash by Termhint: it says so; move it to the Trash in Finder, then remove it again.
- Screen Recording. Not needed (see Accessibility).