SSH not align

[xinxianwu]

SSH not align

[dannyneira]

as a workaround, you can try using adding command ssh to your Settings > Subshell menu, then use command ssh <user@server> to connect to sessions, this will enable Warp features with the subshell method instead of the ssh wrapper.

Or, 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.

https://docs.warp.dev/features/ssh
https://docs.warp.dev/features/subshells

If those don't work, please let us know.

[danielpeng2]

Thanks for reporting, seems like there might be an issue with how we parse the backslash in your username. Are you able to test ssh-ing into a remote machine with a username without a backslash? It'd be helpful to know if there's still alignment issues in that case.

[xinxianwu]

Thanks for reporting, seems like there might be an issue with how we parse the backslash in your username. Are you able to test ssh-ing into a remote machine with a username without a backslash? It'd be helpful to know if there's still alignment issues in that case.

Due to the company's policy on managing domains, our username must have backslashes

[xinxianwu]

as a workaround, you can try using adding command ssh to your Settings > Subshell menu, then use command ssh <user@server> to connect to sessions, this will enable Warp features with the subshell method instead of the ssh wrapper.

Or, 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.

https://docs.warp.dev/features/ssh https://docs.warp.dev/features/subshells

If those don't work, please let us know.

According to my understanding, using the SSH wrapper should enable intelligent prompts and AI services on remote machines. However, I am experiencing display misalignment issues, where commands and window elements do not align properly. Could this be a side effect of using the SSH wrapper?

[danielpeng2]

Could this be a side effect of using the SSH wrapper?

Yeah, it's likely to do with how the SSH wrapper handles bootstrapping the remote shell so it works with Warp. If you try @dannyneira workaround of using command ssh to enable the subshell wrapper instead, does the issue still appear?