Cannot use `RemoteCommand` in ~/.ssh/config, error: Cannot execute command-line and remote command.

I use RemoteCommand in my SSH config to become another user immediately after login with my user.

e.g. RemoteCommand sudo su - <target-user>

And I have different users for different hosts.

With Warp, I get the error Cannot execute command-line and remote command.. So it seems like Warp may be using it's own RemoteCommand in the wrapper. This works fine if I turn the wrapper off. If this is the case, maybe there is a way to combine the two?

Discord username (optional)

No response

Operating System

MacOS

Operating System and Version

14.1.2 (23B92)

Local Shell Version

Fish 3.6.1

Remote Shell Version

N/A

Warp Version

v0.2024.02.27.08.01.stable_03

I have tried commenting out my system & user rcfiles and warp still will not bootstrap

• Yes

Screenshots

No response

Include shell xtrace output

No output in Fish with set WARP_DEBUG_MODE 1

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:e7dfaa84-5fdb-4a00-b754-d8912da923fa

None

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

Start by reproducing the failure with a ~/.ssh/config entry using RemoteCommand sudo su - , comparing Warp with another terminal. Trace Warp's SSH bootstrap or wrapper behavior and determine how it handles the configured RemoteCommand. Done means the configured command works in Warp without the “Cannot execute command-line and remote command” error, with coverage for the reported case.