@EkkoG can you explain a bit the vision using swift-nio-ssh?

The main goal is to move SSH from an external ssh process into Muxy itself.

Compared with the CLI-based approach, this gives us direct control over authentication, session lifecycle, and pane
integration, and it also makes password-based login a first-class path.

It also gives us a better foundation for follow-up flows that are awkward with an external ssh process, such as reusing the
authenticated session context for remote bootstrap/setup steps and building a more consistent password experience around
things like sudo.

That said, this PR is intentionally experimental. It does not assume that swift-nio-ssh is automatically better than the
CLI path in every respect. The tradeoff is that we now own more of the SSH surface ourselves, especially around key handling,
shell compatibility, and recovery.

So the short-term goal is to validate whether this approach is a better fit for Muxy’s remote-project workflow.

@EkkoG For this experimental feature we can ship ssh cli and swift-nio-ssh at the same time and default to ssh cli in the settings

@saeedvaziry Sounds good to me. This approach is definitely better.