Autocomplete in Termius is a fully featured IDE-style autocomplete that suggests completions from many sources such as snippets, commands history, paths, built-in commands with arguments, and passwords for sudo.


Enabling Autocomplete

You don't need to install any third-party packages or dependencies. To enable the autocomplete feature, simply navigate to Settings → Terminal and turn on Autocomplete (beta) toggle. Now you are ready to start. Connect to a host or local terminal and get all benefits of a powerful suggestion system.

Autocomplete in Termius doesn't support PowerShell and CMD.

Command Suggestions

Autocomplete in Termius goes beyond the capabilities of traditional built-in shell autocomplete systems. It uses suggestions from an extensive range of resources, including command history, file paths, and commands with arguments. This results in a comprehensive and context-aware autocomplete system. Save your time by simply starting typing to see suggestions on UI instead of reverse search (CTRL+R) or constant arrow-ups to locate previously used commands.

Snippets Suggestions

Snippets in Termius become even more accessible and efficient when used in conjunction with the Autocomplete feature. They are integrated into autocomplete suggestions, and you can quickly find and execute one without searching for it in the side terminal panel. Start to type a snippet title or part of the command from a script, and Termius promptly display the relevant snippet.

Password Suggestions

The Autocomplete feature in Termius simplifies your workflow by integrating password prompts into suggestions. No more constant manual password entry or copying and pasting complicated passwords from a password manager when executing sudo or other password-protected commands. Termius effectively identifies password requests in a terminal and suggests the appropriate password from hosts and identities in the autocomplete dialog.


In addition to the terminal channel, Termius opens exec channels. It allows the app to fetch information like paths and command history. Sometimes it causes connection drops on the network equipment and machines that are prohibited from exec channel use. During the connection process, it might raise the End of file errors. To avoid this issue, please ensure your network equipment is up to date, and exec channels are allowed.

You can allow exec channels with the following steps:

  1. Open the sshd_config file with your favorite editor. Frequently it is located by path /etc/ssh/sshd_config.
  2. Find a MaxSessions property in the config. It should be commented or set at least to 2.
  3. Save and close the sshd_config file.
  4. Restart the SSH server for the changes to take effect. You can use sudo systemctl restart ssh or sudo service ssh restart.

If the issue is not resolved, please contact our support at

You might also want to read

Add comment

Please sign in to leave a comment.