dannyneira
commented
5 months ago Hi @ShaTie Sorry about this blocker. 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 disable 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.
ShaTie
Dupe Check
Describe the bug
When using the Warp terminal, there is an issue where SSH host suggestions are incorrectly parsed if the hosts listed in the known_hosts file have custom ports specified. The terminal fails to recognize and handle the custom port format correctly, leading to connection errors.
To reproduce
Expected behavior
The SSH suggestion feature should correctly parse and display hosts with custom ports, allowing seamless connection without manual input corrections. Add the ability to disable hints from known_hosts
Screenshots
Operating system
MacOS
Operating system and version
Sonoma 14.5 (23F79)
Shell Version
zsh 5.9 (x86_64-apple-darwin23.0)
Current Warp version
v0.2024.05.28.08.02.stable_00
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
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:b9d78064-c89e-4973-b153-5178a31ee54e
None