inshellisense

inshellisense provides IDE style autocomplete for shells. It's a terminal native runtime for autocomplete which has support for 600+ command line tools. inshellisense supports Windows, Linux, & macOS.

Getting Started

Requirements

• Node.js 20.X, 18.X, 16.X (16.6.0 >=)

Installation

npm install -g @microsoft/inshellisense

Quickstart

After completing the installation, you can run is to start the autocomplete session for your desired shell. Additionally, inshellisense is also aliased under inshellisense after installation.

Shell Plugin

If you'd like to automatically start inshellisense when you open your shell, run the respective command for your shell. After running the command, inshellisense will automatically open when you start any new shell session:

# bash
is init bash >> ~/.bashrc

# zsh
is init zsh >> ~/.zshrc

# fish
is init fish >> ~/.config/fish/config.fish

# pwsh
is init pwsh >> $profile

# powershell
is init powershell >> $profile

# xonsh
is init xonsh >> ~/.xonshrc

# nushell
is init nu >> $nu.env-path

Usage

| Action | Command | Description | | ------------------------------------- | ------- | ------------------------------------------------ | | Start | is | Start inshellisense session on the current shell | | Stop | exit | Stop inshellisense session on the current shell | | Check If Inside Inshellisense Session | is -c | Check if shell inside inshellisense session |

Keybindings

All other keys are passed through to the shell. The keybindings below are only captured when the inshellisense suggestions are visible, otherwise they are passed through to the shell as well. These can be customized in the config.

| Action | Keybinding | | ------------------------- | -------------- | | Accept Current Suggestion | tab | | View Next Suggestion | ↓ | | View Previous Suggestion | ↑ | | Dismiss Suggestions | esc |

Integrations

inshellisense supports the following shells:

• bash
• zsh
• fish
• pwsh
• powershell (Windows Powershell)
• cmd (experimental)
• xonsh
• nushell

Configuration

All configuration is done through a toml file located at ~/.inshellisenserc. The JSON schema for the configuration file can be found here.

Keybindings

You can customize the keybindings for inshellisense by adding a bindings section to your config file. The following is the default configuration for the keybindings:

[bindings.acceptSuggestion]
key = "tab"
# shift and tab are optional and default to false
shift = false
ctrl = false

[bindings.nextSuggestion]
key = "down"

[bindings.previousSuggestion]
key = "up"

[bindings.dismissSuggestions]
key = "escape"

Key names are matched against the Node.js keypress events.

Custom Prompts (Windows)

If you are using a custom prompt in your shell (anything that is not the default PS1), you will need to set up a custom prompt in the inshellisense config file. This is because Windows strips details from your prompt which are required for inshellisense to work. To do this, update your config file in your home directory and add the following configuration:

[[prompt.bash]]
regex = "(?<prompt>^>\\s*)" # the prompt match group will be used to detect the prompt
postfix = ">" # the postfix is the last expected character in your prompt

This example adds custom prompt detection for bash where the prompt is expected to be only > . You can add similar configurations for other shells as well as well as multiple configurations for each shell.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.