Remote bootstrapper
We do some bootstrapping of the remote device before transferring files and executing commands, and mostly use hermetic @ape tools.
This requires us to transfer the tools to the device on every execution, and the approach isn't very cross-platform (e.g. it doesn't support Windows paths). It would be more efficient (and possibly easier to maintain) to build a CLI in Go (for small footprint) that did this instead.
One way to do this would be to transfer this CLI to the remote using the FileTransferProtocol, then run any CommandProtocol commands through it. This would allow us to implement logging, error handling and profiling in a single place, if we wanted.
Edited by Alex Tercete