Airpipe: Send Files Over CLI Without Touching SCP
Ever needed to quickly toss a file from your dev machine to a remote server, but couldn't remember the SCP syntax? Or maybe you just wanted to send something to a colleague's machine without setting up SSH keys?
You're not alone. That's exactly the pain point Airpipe tries to solve. It's a dead-simple CLI tool for sending and receiving files between machines with minimal friction.
What It Does
Airpipe lets you transfer files directly from your terminal to another machine, no SSH or SCP required. You pipe a file over stdin, specify a destination, and the other side picks it up. It's basically file transfer with the convenience of a pipe.
Here's the gist:
cat somefile.txt | airpipe send <target>
And on the receiving end:
airpipe recv > somefile.txt
That's it. No ports to configure, no keys to manage. Just file transfer that works with your existing shell workflow.
Why It’s Cool
No SCP knowledge needed. SCP flags, recursive copying, and port forwarding are powerful, but often overkill for a quick file handoff. Airpipe abstracts all that away.
Works with pipes. Since it uses stdin/stdout, you can chain it with other commands. Want to compress the file before sending?
tar czf - myfolder | airpipe send. Want to decompress on the other end?airpipe recv | tar xzf -.Simple setup. No server installation. No daemon processes. Just a binary on each machine and you're good.
Great for ephemeral transfers. Think of it like
netcatbut specifically for file transfer, with a cleaner interface and error handling built in.
How to Try It
Head over to the GitHub repo to grab the binary or build from source. The README has install instructions for Linux, macOS, and Windows.
Basic workflow:
- On machine A:
airpipe send -r <recipient-id> - On machine B:
airpipe recv -r <recipient-id>
You'll need a shared "room" identifier, which is just a random string you both agree on. It's like a temporary chatroom for files.