the command is yink

yink on your machine

Send a secret from your terminal. Keep a file share running. Use the client that fits your machine, with or without Node.

Node package

Node.js 22+ · npm

The published @yink-io/yink@0.2.0 client provides share, pull, term, send, receive and revoke. Quick Share uses direct WebRTC where possible with relay fallback; Secure Send needs no optional native module.

install the yink command

npm install -g @yink-io/yink
yink --help
yink share path/to/file
yink pull '<complete link>'
yink send --text-file message.txt

Share and pull install their JavaScript dependencies automatically. The terminal command additionally needs the optional native node-pty module. Secure Send does not.

run it once with npx

npx @yink-io/yink --help
npx @yink-io/yink pull '<complete link>' --list

Keep complete links quoted so their fragment parameters reach yink unchanged.

view @yink-io/yink on npm

portable apps

no runtime install

One file with Python and its dependencies bundled. No Python, Node, package manager or administrator access is needed to run it. You can run it where you downloaded it; installation is optional.

Windows · x64

yink.exe

Secure Send and relay file sharing. Terminal hosting is unavailable on Windows.

download Windows preview
run here or install for your user

After verifying the download, run it from PowerShell:

.\yink.exe --help
.\yink.exe send --text-file message.txt
.\yink.exe install

install copies this local binary to your user directory. Run the exact PATH instruction it prints, then use yink.

Linux · x86-64 · glibc

yink

Secure Send, relay file sharing and a POSIX terminal.

download Linux preview

Tested on Ubuntu 24.04, glibc 2.39. Older glibc, Alpine/musl, ARM and macOS are not validated targets for this binary. Check the build information for your platform.

run here or install for your user

After verifying the download:

chmod u+x ./yink
./yink --help
./yink send --text-file message.txt
./yink install
export PATH="$HOME/.local/bin:$PATH"

The local binary is copied to ~/.local/bin/yink. Installation never fetches a replacement.

scripts

bring your runtime

Readable single-file clients. Download and review the script, verify its checksum, then run it locally.

PowerShell 7+ · .NET

yink.ps1

Secure Send only: send, receive and revoke. Share, pull and terminal commands are unavailable.

download PowerShell script script checksums
run here or install the yink command
pwsh -NoProfile -File ./yink.ps1 --help
pwsh -NoProfile -File ./yink.ps1 send --text-file message.txt
pwsh -NoProfile -File ./yink.ps1 install

install copies the local script and creates a yink launcher. Run the exact safely quoted PATH command it prints. It leaves your profile and execution policy unchanged.

Python 3.11+ · isolated dependencies

yink.py

Secure Send, relay share/pull and POSIX terminal hosting. Needs cryptography and websockets; it is not the self-contained app.

download Python script script checksums
run here or install the yink command

With uv, the script's declared dependencies use an isolated environment:

uv run ./yink.py --help
uv run ./yink.py send --text-file message.txt
uv run ./yink.py install

Source installation uses the current Python interpreter and its dependencies. Keep that environment available, and follow the printed PATH instruction.

use it with an AI

one-time setup

For a single pairing session, paste the invite from the main page into Claude Code or Codex; no install is needed. To give an agent proper yink tools, install the MCP server once on the machine where the agent runs.

macOS or Linux

curl -fsSL https://yink.io/install.sh | sh

Windows PowerShell

irm https://yink.io/install.ps1 | iex

The MCP server runs on the agent's machine so encryption keys stay with that peer instead of the relay. The AI agent guide covers no-install pairing, capabilities and manual setup.

what each client can do

Preview command support
commandPowerShellPython app / scriptNode package
send · receive · revokeyesyesyes
share · pullunavailablerelay onlydirect + relay
termunavailablePOSIX only; no Windows terminaloptional node-pty
installper userper usernpm global
direct WebRTCunavailableunavailableyes

Relay shares stay live only while the hosting process runs and are subject to relay limits. These previews do not promise the npm client's complete transport or command parity.

Rust · under validation A Rust download is not offered yet.

verify before you run

  1. Download the matching SHA256SUMS file alongside your chosen artifact. Each app has its own platform checksums; the scripts share the script checksum list.
  2. Compare the SHA-256 of the local file with its exact filename entry. If the value differs or the entry is missing, stop.
  3. For an app, read BUILD.json for the target and runtime versions, and LICENSES.txt for bundled dependency notices. Then run --help locally.

PowerShell · Windows app example

Get-FileHash ./yink.exe -Algorithm SHA256
Get-Content ./SHA256SUMS

Both 64-character hex values for yink.exe must match. For a script, substitute yink.ps1 or yink.py and use the script checksum list.

Linux · app example

sha256sum --check SHA256SUMS

Run this in the directory containing the Linux app and its checksum file. Continue only when yink: OK is reported.

Want it on PATH? Use the verified local client's install command, then its printed PATH guidance. The exposed command is always yink; after installation, yink install can repeat the local operation. No replacement is fetched.

Send content from a file, stdin or an environment variable. Keep passphrases out of command arguments; use a passphrase file, environment variable or hidden prompt. Receive and revoke links are bearer secrets: quote them and protect them from shell history.