Send text, links and commands between devices

Last updated: 2026-07-30

Relayium can move clipboard-shaped content as well as files: a URL from your phone, a command for another computer, or a multiline code block. Messages are end-to-end encrypted and exist only inside the live session; Relayium never stores them.

The browser and command-line client each support text, but they are separate transports and cannot join each other's pairing codes. Choose one flow below and use it on both ends.

Browser: send a message to an online device

Open relayium.com on both devices. Devices on the same network appear automatically; for different networks, create a browser pairing code from the cross-network page and join it in the other browser.

On the peer card, choose “Send a message”; the recipient must accept before any message content or composer appears.
Compare the six-digit verification code (SAS) on both screens, then type or paste text. Use ⌘/Ctrl+Enter to send.
Each side can send several messages and use Copy on any received message while the session remains open.

CLI: mint a code on one machine, join it on the other

Run relayium text with no code on one machine. It mints a six-character code with your account, prints the exact command the other machine should run, and stays in the session waiting for it. There is no temporary file to send and no extra process to stop.

Run relayium text with that code on the other machine. Interactive mode sends one line per message and asks both people to confirm the SAS. For multiline or byte-exact stdin, pipe it as one message and pass --yes because no terminal is available for the SAS prompt.

# One machine mints the code and waits (relayium login is required once)
relayium text
# Code: K7M4XR   (valid 5 minutes)
# On the other machine:  relayium text K7M4XR

# The other machine joins that code
relayium text K7M4XR

# Send one multiline message exactly as copied (macOS)
pbpaste | relayium text K7M4XR --yes

# Or pipe a file on any shell
cat snippet.txt | relayium text K7M4XR --yes

CLI codes last five minutes and are CLI-to-CLI only; browser codes cannot connect a browser to the CLI.
Only the machine that mints needs a signed-in account. The machine joining the printed code does not sign in.
--yes skips the interactive SAS confirmation, so compare the session another trusted way before using it.

What text transfer is — and is not

Relayium treats the body as UTF-8 plain text. It preserves spaces, tabs, blank lines and line breaks, and does not execute, render Markdown, linkify or preview the content.

Both devices must be online together. There is no offline delivery, inbox, contact list or synchronized chat history.
History is local to the open session and disappears when it ends or the page reloads; the server never stores message bodies.
One message is at most 65,536 UTF-8 bytes. For anything larger, send it as a file instead.

Frequently asked questions

Can Relayium read or recover my messages?

No. Message content is end-to-end encrypted between the two devices and is never stored by Relayium. If the live session ends, there is no server copy to recover.

Can I use a browser on one end and the CLI on the other?

No. Browser and CLI text sessions use different transports and pairing handshakes. Use two browsers or two CLI clients.

Open Relayium on two online devices and move the next thing you would otherwise send to yourself.

Send text now