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.

• 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), we do not set it up for Warp - instead, it works like a normal terminal session.

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

• No touch input support

Please note many tools are incompatible with Warp, as listed here. We have 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:

macOS

1. Remove Warp user login with the following command:

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

1. Login to Warp

Windows

1. Remove any user files with the following command:

Remove-Item $env:LOCALAPPDATA\warp\Warp\data\*-User

1. Login to Warp

Linux

1. Remove Warp user login with your keychain manager (gnome-keyring, kwallet, etc.). Search for dev.warp.Warp and delete the User password/secret.

2. Remove any user files with the following command:

rm -f ${XDG_STATE_HOME:-$HOME/.local/state}/warp-terminal/*-User

1. Login to Warp

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

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, etc. we have to build 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.

You can disable the conflicting settings for Warp using this flag: $TERM_PROGRAM != "WarpTerminal", see below for a full example.

We currently don't have support for multi-line custom prompts in bash, only zsh and fish. Unlike typical terminals which are essentially continuous character grids, each section of Warp is its own (separate) UI element. Warps default prompt does not support multi-line or right-sided prompts at this time. Improving the native Prompt is on the roadmap, however. Please see our Prompt page for more information on custom prompts.

Debugging

If Warp is not working with your dotfile configuration,

You can quickly set up clean configs by putting ZDOTDIR=/ in a ~/.zshenv file. This forces zsh to run with zero configs.

Zsh loads your configuration settings in this order:

$ZDOTDIR/.zshenv
$ZDOTDIR/.zprofile
$ZDOTDIR/.zshrc
$ZDOTDIR/.zlogin
$ZDOTDIR/.zlogout

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. If you find an incompatible tool please email us at [e-mail]

# bash and zsh
if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
##### WHAT YOU WANT TO DISABLE FOR WARP - BELOW
    # Unsupported plugin/prompt code here, i.e.
    test -e "${HOME}/.iterm2_shell_integration.zsh" && source "${HOME}/.iterm2_shell_integration.zsh" || true
##### WHAT YOU WANT TO DISABLE FOR WARP - ABOVE
fi

# fish
if test "$TERM_PROGRAM" != "WarpTerminal"
##### WHAT YOU WANT TO DISABLE FOR WARP - BELOW
    # Unsupported plugin/prompt code here i.e. 
    test -e {$HOME}/.iterm2_shell_integration.fish ; and source {$HOME}/.iterm2_shell_integration.fish
##### WHAT YOU WANT TO DISABLE FOR WARP - ABOVE
end

List of incompatible tools

Since Warp has an Input Editor that wraps around the shell, the following inexhaustive list of plugins or tools can cause potential conflict given extra bytes coming into the PTY:

• 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
• Starship settings
• Potentially more, this is an inexhaustive list ...

macOS

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.

• If the above doesn't work, uninstall Warp, then re-install Warp.

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.

Windows

Unsupported in Warp on Windows

The following feature are not supported in Warp on Windows. Please track the relevant GitHub issues linked below for any changes:

• cmd.exe or fish shells

Warp won't run or render on Windows

We're tracking some issues on Windows where Warp crashes on startup or doesn't render, with some possible workarounds below. If none of the workarounds help, please open a new GitHub issue and include logs, installation (Baremetal or VM, x86_64 or ARM64), and the issue you had.

• Graphics

  • You can select the graphics backend used to render new Warp windows in the Settings menu, under Features > System > Preferred graphics backend.

  • You can also opt to render new Warp windows with an integrated GPU, under Features > System > Prefer rendering new windows with integrated GPU (low power).

Crash on opening a Launch configuration or doesn't become transparent on Windows

When a user has an Nvidia 572.xx or AMD 23.10.x drivers or above, Warp may crash when trying to open a Launch Configuration, or Warp fails to become transparent (opacity setting doesn't work). These are known limitations of the graphics drivers. We're investigating the issues and will updated on the GitHub issues above. You can workaround this by forcing the graphics backend to Vulkan or OpenGL by running the following from another terminal and setting your GPU driver Vulkan/OpenGL render method setting to "Prefer Native", or using the DX12 backend:

# Run if Warp on Windows is installed for a single user
$env:WGPU_BACKEND="vulkan,gl"; & "$env:LOCALAPPDATA\Programs\Warp\warp.exe"

# Run if Warp on Windows is installed for all users
$env:WGPU_BACKEND="vulkan,gl"; & "$env:PROGRAMFILES\Warp\warp.exe"

Linux

Warp won't run or render on Linux

We're tracking some issues on Linux where a Warp window doesn't show/render and won't run in Virtual Machines, over remote desktops, or on WSL. Some possible workarounds are below. If none of the workarounds help, please open a new GitHub issue and include logs with your Linux distro, installation (WSL, Baremetal or VM, x86_64 or ARM64), and the issue you had.

• Many package install examples are for Ubuntu using apt, your distro may use different commands (dnf, pacman, zypper) or package names.

• GPU Drivers and Default GPU / Graphics API environmental variables are system-dependent. e.g. AMD vs NVIDIA and OpenGL vs Vulkan

• System

  • Installing or Updating Xorg / Wayland: sudo apt install xserver-xorg / sudo apt install wayland
  • Installing Hack font on WSL and VMs: sudo apt install fonts-hack
  • Install WSL utilities: sudo apt install wslu
  • Install Mesa utilities: sudo apt install mesa-utils

  • Install Mesa Vulkan drivers: sudo apt install mesa-vulkan-drivers

  • If unable to use the file picker: sudo apt install xdg-desktop-portal xdg-desktop-portal-gtk zenity

  • If unable to copy-paste: sudo apt install wl-clipboard

• Graphics

  • Install or Update your GPU driver: e.g. NVIDIA 535.x or below drivers

    • For Ubuntu: sudo ubuntu-drivers install

    • For Fedora: sudo dnf install akmod-nvidia

    • For Arch Linux: sudo pacman -S nvidia

    • For openSUSE: sudo zypper install x11-video-nvidiaG05

  • Use Low Power (integrated) GPU in ~/.config/warp-terminal/user_preferences.json file: {"prefs":{"PreferLowPowerGPU": "true",}}. The low-power workaround is particularly helpful if you see Unrecognized device error ERROR_INITIALIZATION_FAILED in warp.log.
• Environmental Variables

  • Prefix warp-terminal with the variables (multiple can be used), and once you confirm they work, export them in your .profile/.zprofile to load on startup:

    • Default to Wayland: WARP_ENABLE_WAYLAND=1
    • Set Default GPU for WSL: e.g. MESA_D3D12_DEFAULT_ADAPTER_NAME=NVIDIA
    • Set Graphics APIs: e.g. WGPU_BACKEND=gl

Update fails after upgrading Linux

Some Linux distros may modify Warp's package repository during the the OS upgrades. We're aware of this on Ubuntu, but this may affect other Linux distros. We're tracking this issue on GitHub here. To workaround this issue, manually add the repository to update Warp. The Ubuntu example is below:

sudo apt-get install wget gpg
wget -qO- https://releases.warp.dev/linux/keys/warp.asc | gpg --dearmor > warpdotdev.gpg
sudo install -D -o root -g root -m 644 warpdotdev.gpg /etc/apt/keyrings/warpdotdev.gpg
sudo sh -c 'echo "deb [arch=amd64 signed-by=/etc/apt/keyrings/warpdotdev.gpg] https://releases.warp.dev/linux/deb stable main" > /etc/apt/sources.list.d/warpdotdev.list'
rm warpdotdev.gpg
sudo apt update && sudo apt install warp-terminal

See the instructions for other Linux distros on our Quick Start Guide.