SSH host management needs the desktop bridge. In Settings → Remote Instances, enter an SSH command or select a saved host from the local SSH configuration. A host pattern needs a concrete destination before connecting.
Decide who starts Yuri remotely
Choose a managed connection when Yuri should arrange its remote service. Choose an external service when you already run the destination instance. Save the host and connect; the progress stages distinguish authentication, setup and forwarding failures.
Once ready, confirm the remote project directory. The window is local, but the workspace is on the destination computer. If a Yuri host is already reachable without SSH, a pairing link may be sufficient.
Add a path for another service
The instance's port-forward controls support local (-L), remote (-R) and dynamic (-D) forwarding. A local forward exposes a remote service on your computer; a remote forward reverses that direction; a dynamic forward provides a SOCKS proxy.
Use a loopback bind address for a forward intended only for your own computer. For a phone, pair with the remote Yuri host itself—the mobile client does not run the desktop SSH manager.
Bring the model setup along
Ready managed SSH connections expose configuration sync. When Magpie is detected on the chosen source, the wizard offers it as a separate optional selection, including supported configuration and authorizations. Follow the Magpie transfer guide and check the destination result before relying on it.