Known Issues
To see a complete list of issues and feature requests, please visit our GitHub issues page.
Warp doesn't support
PROMPT_COMMAND
in bash right now, to set a custom prompt usePS1
.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.
Links to popular GitHub issues:
SSH
To enable Blocks over SSH, Warp uses an SSH Wrapper function; navigate to settings > features if you need to disable it.
Note: You'll need to start a new session before a change is reflected or try invoking the SSH binary directly: command ssh
.
There is also a known issue with the SSH Wrapper not working in Windows SSH sessions. You can workaround this by installing Cygwin on the Windows machine you'd like to connect to.
Online features don't work
There is a known issue that can occur that causes online features to break (Warp AI, AI Command Suggestions, Block Sharing, Refer a Friend, etc. ). This is due to the login token going stale, typically due to a password change, and can be resolved by the following steps:
Remove Warp user login with
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.
fish shell read
command
read
commandThere 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.
List of incompatible tools
test -e "${HOME}/.iterm2_shell_integration.zsh" && source "${HOME}/.iterm2_shell_integration.zsh" || true
eval "$(termium shell-hook show post)"
thefuck experimental instant mode
eval $(thefuck --alias --enable-experimental-instant-mode)
[ -f ${HOME}/bin/fubectl.source ] && source ${HOME}/bin/fubectl.source
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.
FIG,
z
,zsh-autocomplete
,compdef
,compinit
, prezto utility module, or other shell-based completion plugins or definitions.OH-MY-ZSH-THEMES
e.g. avit, spaceship, maybe more ...
OH-MY-ZSH-PLUGINS
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
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:
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 feedback@warp.dev
Fig
Bash and Fig
A recent version of Fig (happens as of 1.0.56 - and may also happen on earlier versions) updated the bash rcfiles in a way that prevents Warp from bootstrapping.
In order to work around this, you can disable this logic for Warp. Note that you might have to do this for .bash_profile
and .bashrc
.
Also, Fig has a tendency to re-write these lines in these files when it updates - so you might have to do this multiple times if you are using Fig actively.
.bash_profile
.bashrc
fish and Fig
Some older installations of Fig (most notably prior to September 2021) include startup scripts that are incompatible with Warp's bootstrap process. As described above in Configuring and debugging your RC files, those scripts should be gated on a check of the TERM_PROGRAM
environment variable. The two important files in this case are:
~/.config/fish/conf.d/00_fig_pre.fish
~/.config/fish/conf.d/99_fig_post.fish
macOS
Auto-Update on macOS Ventura
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 Rosetta
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.
Linux
Linux Workarounds
We're tracking some issues for Linux where a Warp window doesn't show/render, Won't run in Virtual Machines, over remote desktops, or on WSL.
If any of the workarounds help, please comment on this GitHub issue with your Linux distro, installation (WSL, Baremetal or VM, x86 or ARM), the issue you had, the workaround that fixed it, and any other workarounds not listed.
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 Hack font:
sudo apt install fonts-hack
Install WSL utilities
Install Mesa utilities:
sudo apt install mesa-utils
Install Mesa Vulkan drivers:
sudo apt install mesa-vulkan-drivers
Fallback to Mesa v23.x from Mesa v24
Graphics
Install or Update your GPU driver: e.g. NVIDIA
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 seeUnrecognized 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: e.g.
MESA_D3D12_DEFAULT_ADAPTER_NAME=NVIDIA
Set Graphics APIs: e.g.
WGPU_BACKEND=gl
Last updated