Save ssh sessions into Launch Configurations

[dannyneira]

Discord username (optional)

Danny N#2929

Describe the solution you'd like?

When saving Launch Configurations, Warp doesn't save current ssh sessions. It saves them in the yaml file cwd as "". I think the ability to add/record configurations should include active ssh sessions, possibly via the command - exec option.

Is your feature request related to a problem? Please describe.

No response

Additional context

As a workaround, you can manually enter ssh user@www.example.com into the command - exec section of the yaml file. Please see example here: https://docs.warp.dev/features/sessions/launch-configurations#commands

How important is this feature to you?

3

Warp Internal (ignore) - linear-label:770f6576-d6c0-4e4f-a259-fc64b5156087

No response

[dannyneira]

Please +1 this request as it helps us gauge interest. We will post any updates here.

[f1rstC0de]

Yes, this is a very important feature, the absence of which makes the daily use of warp difficult. But it will be even cooler if it becomes possible not only to save open ssh sessions in the Launch Configuration, but also to assign them the same credentials once, for the entire group. For example, like this:

name: My Dev
windows:
  - tabs:
    - credentionals:
        user: user1
        password: password1
        key: key1
        - layout:
            cwd: ""
        - layout:
            cwd: ""
        - layout:
            cwd: ""

This is a very cool feature that makes life much easier for those who work with cluster systems. Perhaps it makes sense to make a separate menu for storing ssh sessions, with the ability to combine into groups like Termius.

[dannyneira]

@f1rstC0de As a workaround, you can manually enter ssh user@www.example.com into the command - exec section of the yaml file. Please see an example here: https://docs.warp.dev/features/sessions/launch-configurations#commands

It's a bit of a manual process, but I hope this helps!

[f1rstC0de]

I understand that I can, but it's very inconvenient when the number of hosts is constantly growing and they number in the hundreds. Therefore, I would like to have a full-time ability to conveniently save the parameters of ssh sessions, and ideally, in general, be able to specify connection parameters for a group of hosts (I already cited Termius as an example).

[AaronDovTurkel]

@f1rstC0de As a workaround, you can manually enter ssh user@www.example.com into the command - exec section of the yaml file. Please see an example here: https://docs.warp.dev/features/sessions/launch-configurations#commands

It's a bit of a manual process, but I hope this helps!

The issue with this approach is that you cant run any follow up commands after logging into the remote host. The exec param will just chain the commands in the previous session.