[FEATURE] Remote execution mode

[danielkza]

Feature Summary

In development environments where all acess to internal networks happens via a jump host or remote VM, it would be great to have a mode where all features are "tunneled' via SSH. So we would get Atuin history from the remote, connect to databases via SSH tunnel, all commands run remotely (even "local" commands, i.e. the remote machine becomes localhost)

Problem/Use Case

Allows working in environments where the desktops have no access to internal networks.

Proposed Solution

A runbook can be configured such that every action is tunneled or execute in a remote host. There should be no possibility to run any actions locally, so the experience is clear and uniform,

Current Workaround

It's probably possible to set up SSH port forwarding manually and use SSH blocks, but it might require users to take extra external steps that make the experience less convenient.

Detailed Description

User Interface

Ideally, have a per-runbook configured SSH remote host, possibly a list of forwarded ports and/or host aliases.

Integration Points

Would this feature need to integrate with:

• Shell/Terminal
• Database clients
• HTTP/API calls
• File system
• External tools (specify): ___
• Other: Basically everything

Alternatives Considered

I'm just starting to evaluate Atuin desktop, but this execution model is basically required in some development environments.

Additional Context

• Priority: High
• Frequency: Daily
• Team Impact: Entire team, many companies

Related Issues/Discussions

N/A

Implementation Notes

N/A, I don't know enough to opine