Known Issues

Warp issues along with workarounds and solutions.

To see a complete list of Warp issues and feature requests, please visit our GitHub issues page.

Please note that there are tools that are incompatible with Warp, as listed below. You can find debugging information in this section.

General

SSH

To enable Blocks over SSH, Warp uses an SSH Wrapper function; navigate to settings > features if you need to disable it. Please see Troubleshooting Legacy SSH for more info on workarounds to SSH issues, or see the new SSH Page for more on the upcoming features.

Online features don't work

There is a known issue that can occur that causes online features to break (Warp AI, Generate, Block Sharing, Refer a Friend ). This is due to the login token going stale, typically due to a password change, and can be resolved by the following steps:

  1. Remove Warp user login with the following command:

sudo security delete-generic-password -l "dev.warp.Warp-Stable" $HOME/Library/Keychains/login.keychain

English-only UI

Nov 2021: We have added character support for Chinese, Korean, and Japanese, but our UI currently only supports English.

Abnormal rendering of Chinese characters

If you notice issues with the terminal rendering Chinese characters (i.e. #3366). Please try adding the following lines to your rc file.

export LC_ALL=zh_CN.UTF-8
export LANG=zh_CN.UTF-8

Misc.

  • When you SSH, we start a bash shell on the remote host. We built a wrapper around SSH to make Warp features possible.

  • If your default shell is zsh, your aliases typically do not transfer over. Other shells are unsupported for now.

  • When you open a non-shell-based subshell (REPL), Warp does not modify the environment — it behaves like a standard terminal session.

  • Warp may become unresponsive if it doesn't have permission to access the folders.

Agent Mode

  • Note that Agent Mode blocks are not shareable during session sharing. Participants will be able to share regular shell commands that are run, but will not be able to share AI interactions (requested commands, AI blocks, etc.).

  • Block actions such as Block Sharing are not available on Agent Mode AI blocks.

  • Agents do not have up-to-date information on several commands’ completion specs

  • Agent Mode works better with Warp's default prompt settings, where the prompt starts on a new line, than it does with a same-line prompt. If you are using the same-line prompt, the cursor will jump from the end of the single line to the start of the input box when you switch to Agent Mode.

Shells

fish shell read command

There is an issue in fish shell version 3.6 and below that causes the read built-in command to break Warp's integration with fish. This means that using read directly or any fish scripts that call read will not work as expected in Warp. That issue is resolved in the fish repository and so should be fixed in the next release of fish itself. We recommend upgrading fish to the most recent version to resolve this issue.

Warp shell loads slowly due to EDR

If you comment out the rc files (i.e. ~/.zshrc, ~/.bashrc, ~/.config/fish/config.fish), and still notice a slowdown on loading the shell. It could be due to an Endpoint Detection and Response or EDR (i.e. Sentinel One, CrowdStrike, Carbon Black) causing the issue. Please restart your system and see if the issue persists. If so, please Send us Feedback and provide details of your EDR, OS, shell, etc.

Configuring and debugging your RC files

To support Blocks (custom hooks), a native Input Editor experience, AI blocks, etc. we have built custom support for a subset of shell functionality (decouple functionality from the shell and move to the terminal). This leads to Warp being incompatible with various tools and plugins. Please see the list of incompatible tools to find the tools that are known not to work with Warp.

Unlike typical terminals which are essentially continuous character grids, each section of Warp is its own (separate) UI element. Please see our Prompt page for more information on custom prompts.

Debugging

If Warp is not working with your dotfile configuration, you can run your shell in Warp with a clean configuration using examples below:

You can set up clean configs for Bash (Bourne Again SHell) by moving or commenting out your .bashrc If Warp starts working correctly then Warp is incompatible with something in the current dotfiles. We can isolate what is incompatible by iteratively disabling sections of our dotfiles with the WarpTerminal flag until we find the culprit. See the list of incompatible tools below and comment them out just for Warp with the following conditionals:

# bash (See ~/.bashrc)
if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
##### WHAT YOU WANT TO DISABLE FOR WARP - BELOW
    # Unsupported plugin/prompt code here, i.e.
##### WHAT YOU WANT TO DISABLE FOR WARP - ABOVE
fi

List of incompatible tools

The following non exhaustive list of plugins, prompts, or tools can cause potential issues in Warp:

  • oh-my-fish, oh-my-bash, or other unsupported shell prompts. See our Custom Prompt Compatibility Table.

  • iterm shell integration

    • test -e "${HOME}/.iterm2_shell_integration.zsh" && source "${HOME}/.iterm2_shell_integration.zsh" || true

  • Termium

    • eval "$(termium shell-hook show pre)"

    • eval "$(termium shell-hook show post)"

  • thefuck experimental instant mode

    • eval $(thefuck --alias --enable-experimental-instant-mode)

  • fubectl

    • [ -f ${HOME}/bin/fubectl.source ] && source ${HOME}/bin/fubectl.source

  • BIND keys

    • bindkey '^j' down-line-or-beginning-search, which causes users to have to hit ENTER twice to run a command.

    • bindkey 'tab' autosuggest-accept, which causes incorrect behavior with autocompletion.

  • z, compdef, compinit, prezto utility module, bash-it, CodeWhisperer or other shell-based completion plugins.

  • OH-MY-ZSH Themes

    • e.g. avit, spaceship, maybe more ...

  • OH-MY-ZSH Plugins

    • e.g. zsh-autosuggestions, zsh-autocomplete, maybe more ...

  • Oh-My-Tmux

  • zsh4h (ZSH for Humans)

  • znap

  • FZF

  • [[ -r "/usr/local/etc/profile.d/bash_completion.sh" ]] && "/usr/local/etc/profile.d/bash_completion.sh"

  • eval "$(rbenv init -)"

  • grml-zsh-config

  • Python virtual environment PS1 settings

  • Potentially more — this is an non exhaustive list. If you find an incompatible tool, please email us at [email protected]

Operating systems

SSH to local network device is denied on macOS

On macOS, you may be denied permission to SSH from Warp into other devices in your local network and see an error like: ssh: connect to host <host_name> port 22: Undefined error: 0. To resolve this issue, go to Mac > System Settings > Privacy & Security > Local Network, and add Warp.

Mac SSH permission error

Unexpected loss of permission on macOS

On macOS, you may see a Operation not permitted error when trying to run commands in directories that have already been granted macOS permissions (Documents, Downloads, Desktop, etc). The best workaround at this time, is to apply any pending Updates so that the new Warp binary has the correct permissions. We are and tracking this issue here.

Permission error on macOS

Auto-Update error on macOS

Warp may have an error opening after auto-update on macOS Ventura. This issue has been resolved for current and future releases of Warp. To avoid the issue, update Warp before you upgrade to macOS Ventura. If you experience an error opening Warp, please try the following:

  • Go to the macOS Applications folder, right-click on Warp, choose Open, then the '"Warp" is damaged' dialog will have the option to click the Open button.

Running x86 commands with macOS

In some cases, CLI applications only work on x86 so you can run Warp with Rosetta on macOS to be able to use them by doing the following.

  • Go to Finder > Applications and search for Warp.

  • Right-click and select Get Info.

  • Then check the box on Open with Rosetta.

Last updated

Was this helpful?