search

warpdotdev / Warp

Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.
https://warp.dev
Other
21.12k stars 362 forks source link

Workflow usage not working when connected to remote ssh shell #5054

Open edg1983 opened 3 months ago

edg1983 commented 3 months ago

Dupe Check

Describe the bug

When connected to a remote shell using SSH, it is not possible to automatically use saved workflows. When I try to use one of them (for example, double-clicking on a saved workflow), I get this error: 'A command in this session is still running'. To clarify

  1. I open Warp and connect to a remote server using ssh user@server
  2. In Warp, connected to the remote shell, I now try to use a saved workflow and the above issue appears.

Everything works fine if I try the same while on my local terminal.

To reproduce

  1. Open Warp and connect to a remote server using ssh user@server
  2. In Warp, connected to the remote shell, now try to use a saved workflow.

Expected behavior

Warp should be able to insert the saved workflow automatically asking to fill the variable as it normally does on local shell.

Screenshots

No response

Operating system

MacOS

Operating system and version

MacOS 13.6.7 (local); CentOS Linux 8 (remote)

Shell Version

zsh 5.9 (local); bash 4.4.19 (remote)

Current Warp version

v0.2024.06.11.08.02.stable_03

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:b9d78064-c89e-4973-b153-5178a31ee54e

None

dannyneira commented 3 months ago

Hi @edg1983 Warp has an SSH Wrapper that enables features (like the blocks, prompt, completions, etc.) on remote machines requiring the default prompt on the remote machine to be either bash or zsh.

As a workaround you can add command ssh to your Settings > Subshells > Added commands menu, then run command ssh <user@server> to connect to remote session, this will attempt to enable Warp features as a subshell.

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.

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

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