Built for AI-to-human and AI-to-AI handoffs.

The last step of every agent task

Agent work ends in a file. It has to reach a person, another agent, or the machine where it's needed. scp needs a key and a reachable port. Cloud drives keep your file on someone else's server. peeza does it in one command.

$ peeza link render-final.mp4
https://g.peeza.app/7XK4M2QD#k=…

$ peeza get 'https://g.peeza.app/7XK4M2QD#k=…'      # another agent, another machine, no account

$ peeza send build.zip --to <device>      # peeza devices lists yours

The link prints alone on stdout. $(peeza link file) is the link. Hand it to a person, or to peeza get on any machine that has peeza.

01A link any human or agent can open

peeza link makes a single-use, end-to-end-encrypted download link. A human opens it in a browser. An agent redeems it with peeza get. No account on either end.

• Single use. The first download spends the link. A copy left in a chat log is worthless.
• The relay does not receive the key (one exception, when you ask for it). The key rides in the link's # fragment, which browsers never send. See the tech page.
• No signup on either end. The receiver clicks, or runs peeza get. That's it.

02Your machines, without SSH

peeza send --to reaches your account's machines, wherever they are. No key on the far machine, no open port, no VPN, no shared network.

• Crosses NAT by itself. Direct peer-to-peer when possible. Otherwise a blind relay carries ciphertext.
• Offline is fine. A machine that's asleep or away receives the file when it returns.
• An agent on the far machine? It sees the file land with peeza watch --json, and finds it with peeza ls. Two agents, two machines, one account.
• Same desk? peeza send --nearby uses the local network. No internet, no relay, no account.

03The transfer survives the agent

A background engine owns each transfer, not the process that started it.

The agent can exit, the session end, the laptop reboot. The delivery goes on. Transfer state is saved first. An interrupted transfer resumes from the last byte written, not from zero.

04Made to be scripted

Built for machines from day one.

• Verbs block until the transfer is actionable. They exit with documented codes (0–6). A script never has to guess whether the send took.
• --json makes every answer machine-readable. peeza ls and peeza watch report live transfer state.
• An MCP server (peezad mcp) gives agent frameworks the same operations. You opt in. It is never on by default.
• Also: peeza get '<link>' redeems a link. Quote it: the #k= fragment is the key, and an unquoted # is a shell comment. peeza park packages a file and holds it with no network contact. peeza accept starts a held transfer. --against <path> on get or accept sends only what changed from a file you already have. --wait complete returns when the bytes have arrived, not when the transfer is actionable.

Every verb, flag, exit code and MCP tool: the command-line reference, which is the binary's own peeza help, published as is.

05The same security, whoever's driving

Agent or person, every transfer is encrypted the same way: end to end, on every path, always.

Files go straight between devices. A relay, when needed, forwards only ciphertext it cannot read and stores nothing. The limits are in our published protocol, including one exception, when you ask for it. Details: the tech page and the privacy policy.

06Install

The command line comes with the desktop app. Install it from a terminal or from the app. On a Mac that already has peeza, turn it on in Settings › General › Command line.

macOS 14 or later, with Homebrew

brew install ercwilcom/tap/peeza

Installs the app and the peeza command. The app updates itself.

Ubuntu 22.04, Debian 12 or later

sudo wget -qO /usr/share/keyrings/peeza-archive-keyring.gpg https://apt.peeza.app/peeza-archive-keyring.gpg
sudo wget -qO /etc/apt/sources.list.d/peeza.sources https://apt.peeza.app/peeza.sources
sudo apt update && sudo apt install peeza

Adds peeza's apt repository. Updates come with your system's.

Windows 10 (2004) or later

No package manager. The installer adds the peeza command.

All downloads, checksums and the Flatpak are on peeza.app/download.

07Before the first verb

Check these instead of guessing.

• An engine must be running. The desktop app runs it. On a Mac, the command line starts it through the app's launchd job. On Linux and Windows it starts nothing: open the app once, or run the engine yourself (/usr/lib/peeza-app/peezad --port 7411 on a .deb install; the exit-3 message names the path on any install). With no engine, every verb exits 3 and says why. peeza health checks without a token.
• No account for links, parking or nearby. peeza link, peeza park, peeza get and send --nearby work signed out.
• Machines and teams need an approved account. send --to, send --team and peeza devices need peeza connect on an approved account. Accounts are a closed beta, approved by hand. peeza whoami shows this machine's state.
• Sizes. A direct transfer has no size limit. A link that goes through the relay carries up to 2 GB a month per device without an account, and the account's relay allowance with one. Figures: the relay page.
• The engine outlives the agent, not the machine. A container or sandbox that exits takes its engine with it. Run the engine where the files should keep moving.