#Using subterminals while ssh'ed

4 messages · Page 1 of 1 (latest)

zealous monolith
#

During a recent ssh session in windows while ssh'ed a I opened a psql subterminal. Now usually this works just fine in macos or while not - ssh'ed but in this instance I couldn't use warp as text entry in the

psql #

terminal. Trying to put anything into the entry box and pressing enter would do nothing, the text would remain there.

Is this a known issue/limitation?

small kindleBOT
#

Hi @zealous monolith. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

Yes, this is a known issue and limitation with Warp, especially when using SSH sessions and subshells (like psql) on Windows.

Several users have reported problems where, after SSH'ing into a remote server and opening a subshell or REPL (such as psql), text entry and the Enter key do not work as expected. This issue is specific to Warp and does not occur in other terminals like iTerm2 or the default macOS Terminal. The problem is more pronounced on Windows, where the underlying PTY (ConPTY) and Warp's shell integration can introduce additional complications with escape sequences and subshell handling.

For example, users have described situations where they cannot paste or enter long queries into psql, or where pressing Enter in a subshell (including psql) does nothing—the text remains in the input box and is not executed. This behavior has been acknowledged by the Warp team and is related to how Warp handles SSH sessions, subshells, and its custom shell integration features. Workarounds such as disabling the SSH Wrapper or using the subshell feature with specific settings have been suggested, but these do not always resolve issues with interactive REPLs like psql in SSH sessions, especially on Windows. The Warp team is actively working on improving SSH and subshell support, but these limitations currently existcopying / pasting in a ssh session doesn't work as expected, Warp can not automatically "Warpify" subshells when use RC file, Known Issues.

#

If you encounter this issue, you can try the following workarounds:

  • Disable the SSH Wrapper in Warp's settings (Settings > Features).
  • Use the "command ssh" workaround to trigger subshell logic instead of the SSH wrapper.
  • If possible, use a different terminal for workflows that require interactive REPLs over SSH until these issues are resolved.

If these workarounds do not help, you are likely hitting a current limitation of Warp's SSH and subshell integration, particularly on Windows. The team is aware and improvements are in progress.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: