If you're using zsh on the remote host, Warp creates a temp folder to act as the ZDOTDIR during the bootstrapping process and removes it when the shell is set up.
We create a wrapper (around /usr/bin/ssh) to set up the shell for Warp's feature set. We authenticate normally using /usr/bin/ssh, and bootstrap the remote shell to work with Warp Blocks and the Input Editor. You can opt out of this functionality by invoking command ssh directly.
Warp takes over the prompt which enables us to build a modern input editor.
Warp configures histcontrol to ignore commands with leading spaces. We do this so our bootstrapping code does not clutter the history.
You can see the SSH wrapper by using which warp_ssh_helper in zsh, type warp_ssh_helper in bash.
Note: The ssh wrapper is only initialized on your local machine. We don’t currently support bootstrapping nested ssh sessions.
Warp Completions for ssh show entries in ~/.ssh/config and ~/.ssh/known_hosts
channel 2: open failed: connect failed: open failed
If you're seeing these errors, you may have some config on your server (usually in /etc/ssh/sshd_config) preventing Warp's ControlMaster connection from working. In this state, completions that require information from your remote host won't work and your history also won't work.
You should ensure that MaxSessions is either commented out or is at least 2.
Write access in /etc/ssh/ typically requires sudo access. After any edits, you'd also need to restart the sshd daemon.