dannyneira
commented
6 days ago Hi @miohtama Warp has an SSH Wrapper that enables features (like the blocks, prompt, completions, etc.) on remote machines requiring the default prompt on the remote machine to be either bash or zsh.
As a workaround you can add command ssh to your Settings > Subshells > Added commands menu, then run command ssh <user@server> to connect to remote session, this will attempt to enable Warp features as a subshell.
You can also try disabling the SSH Wrapper by navigating to Settings > Features. Blocks will stop working but with it disabling, SSH should work as normal.
Related docs: https://docs.warp.dev/features/ssh https://docs.warp.dev/features/subshells
If those don't work, please let us know.
Dupe Check
Operating System
MacOS
Operating System and Version
13.2.1
Local Shell Version
zsh 5.9
Remote Shell Version
zsh 5.9
Warp Version
v0.2024.06.18.08.02.stable_03
I have tried commenting out my system & user rcfiles and warp still will not bootstrap
Screenshots
No response
Include shell xtrace output
There is no such version as 3.31?
https://docs.warp.dev/getting-started/changelog
The command does not output anything besides normal SSH.
Does this block you from using Warp daily?
No
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore) - linear-label:e7dfaa84-5fdb-4a00-b754-d8912da923fa
None
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
None