deft canopy
I am unable to do anything until I enter clear in the terminal, I have to type in anything then cancel the command with ^+c and then use the clear command and only then the session can be used for anything else, I have no idea why this is happening and this has essentially made all my launch configs useless, please help
tardy ravenBOT
Hi @deft canopy. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
The issue you're experiencing with Warp v0.2025.08.13.08.12.stable_02—where executing any command dumps shell code into the terminal and the shell gets stuck—has been reported by other users as well. This appears to be a regression introduced in this specific version, affecting both macOS and Linux users. The problem persists even after reinstalling Warp or restarting your computer, and it also affects the Preview version of Warp. Users have described needing to type a command, cancel it with Ctrl+C, and then use clear to regain some functionality, but this is only a temporary workaround and does not resolve the underlying issue.
The Warp team is aware of this bug and is actively investigating it. In the meantime, a recommended workaround is to downgrade to the previous stable version, which does not exhibit this behavior. You can download the last working release from this link:
Warp v0.2025.08.06.08.12.stable_01 (macOS)
If you're on Linux, you may need to check the Warp releases page for the appropriate package for your system.
Additionally, some users have found that issues like this can be triggered or exacerbated by certain shell configurations or plugins (such as custom prompts, Oh My Zsh, Prezto, or injected shell integrations). If you want to help debug or try to isolate the problem, you can temporarily run your shell with minimal configuration. For zsh, you can do this by running:
echo 'ZDOTDIR=/' > ~/.zshenv
This will force zsh to start with zero configs. If this resolves the issue, you can then selectively re-enable parts of your configuration to find the culprit. You can also use conditional statements in your dotfiles to disable problematic plugins or themes only when running in Warp:
if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
# What you want to disable here
fi
See more details in the Warp docs and list of incompatible tools.
For now, downgrading to the previous version is the most reliable solution until a fix is released for the current version. You can subscribe to the open issue tracking this bug for updates from the Warp team.