Server's welcome message appears in command history following an SSH connect

[jakehowlett]

Discord username (optional)

No response

Describe the bug

If I connect via SSH to a remote server and the server responds with the following welcome message. This message then becomes part of my command history. So, if I press the up arrow to cycle through my recent commands, this whole message pops up and the is a little jarring at first.

Maybe it's a feature? Seems like a bug to me.

Welcome to Ubuntu 22.04.1 LTS (GNU/Linux 5.15.0-47-generic x86_64)

• Documentation: https://help.ubuntu.com
• Management: https://landscape.canonical.com
• Support: https://ubuntu.com/advantage

System information as of Fri Aug 11 08:08:33 AM UTC 2023

System load: 0.240234375 Usage of /: 33.9% of 48.64GB Memory usage: 64% Swap usage: 50% Processes: 120 Users logged in: 1

108 updates can be applied immediately. 1 of these updates is a standard security update. To see these additional updates run: apt list --upgradable

*** System restart required ***`

To reproduce

SSH to a server. Press up arrow to see most recent command sent. It is (in my case) the server's welcome message.

Expected behavior

Not the welcome message

Screenshots

Operating system

MacOS

Operating system and version

13.0.0

Shell Version

No response

Current Warp version

v0.2023.08.08.08.04.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?

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:b8107fdf-ba31-488d-b103-d271c89cac3e

None

[warpdotdev-devx[bot]]

hey @jakehowlett Thanks for letting us know, we have a related issue here #1160. This may be due to the bootstrapping that takes place when you connect to a remote machine with SSH so it may not be a bug, but intentional for the bootstrapping process.

As a workaround, you can try running /usr/bin/ssh directly and then set the automatically Warpify subshell line in your remote server rc files.

To anyone else facing this issue, please add a 👍 to the original post at the top or comment with your details, and subscribe if you'd like to be notified.

[eltoddo]

This definitely has been happening to me since day one of using Warp. However it was one of the main reasons I basically didn't use Warp as my daily driver terminal. Made it seem like Warp wasn't ready yet. Finally got over that and started putting up with the annoyance, as I try to embrace Warp as my main terminal app.

It's really frustrating for me though. Corporate policies dictate agressive timeout of VPN connections, so around 50% of the time I come back to my laptop, I need to reconnect all my sessions and are met by numerous identical walls of text that from MoTD on each pane. Worse, Warp thinks these are commands, so filtering the block does nothing!

It's a relatively minor issue, but it really makes it hard to regain context when I already have enough of an uphill battle to regain necessary context to resume workflow. Being able to set filters to block commands, and having a list of automatic filters to apply to all (new?) blocks would be a really nice feature to address this.