What problem does it solve? Agents and users often need to inspect logs, check services, or move files on machines that have no interactive session, and hand-rolled ssh/scp commands are error-prone with quoting, authentication prompts, and inconsistent login environments. ## Core Features & Use Cases - Non-interactive command execution: remote run <host> -- <cmd> executes commands under a remote login shell with BatchMode, ControlMaster reuse, and propagated exit codes. - File transfer: remote get and remote put move files between hosts without opening an interactive SSH session, supporting stdout streaming or explicit output paths. - Use Case: A dispatched coding agent needs evidence from a production box: it runs remote run workbox -- journalctl -u myapp -n 200 --no-pager, pulls the error log with remote get, and writes its findings report on the local machine. ## Quick Start Ask the agent to check the application logs on the workbox host using the remote run command and summarize the findings in a local report file.