🤖 Filed automatically by @ozdotdev on behalf of @BHolmesDev.
Source: https://x.com/BHolmesDev/status/2062625986684792959
Summary
After exiting an SSH session in Warp, the local shell sometimes auto-executes tmux-style new-window commands, causing zsh: command not found: new-window errors.
Problem
When users exit an SSH session after a recent Warp update, commands like new-window (typically associated with tmux) are unexpectedly executed in the local shell, resulting in command not found errors.
Expected behavior
Exiting an SSH session should cleanly return to the local shell without executing any additional commands.
Actual behavior
The local shell auto-runs tmux-style new-window commands after SSH session exit, failing with zsh: command not found: new-window.
Reproduction hints
- After recent Warp update
- Exit an SSH session
- Observe whether tmux-style commands execute in the local shell
Source thread
@sandipkurmi0: Hey @warpdotdev, after the recent Warp update, when I exit an SSH session, my local shell sometimes auto-runs tmux-style new-window commands and ends with zsh: command not found: new-window. Is this a Warp/tmux config issue or a bug? #Warp #Terminal https://t.co/MHARXoU7UL
Summary
After exiting an SSH session in Warp, the local shell sometimes auto-executes tmux-style
new-windowcommands, causingzsh: command not found: new-windowerrors.Problem
When users exit an SSH session after a recent Warp update, commands like
new-window(typically associated with tmux) are unexpectedly executed in the local shell, resulting in command not found errors.Expected behavior
Exiting an SSH session should cleanly return to the local shell without executing any additional commands.
Actual behavior
The local shell auto-runs tmux-style
new-windowcommands after SSH session exit, failing withzsh: command not found: new-window.Reproduction hints
Source thread