Engineering preview Diagnostic stays on this machine Mac app is the pairing surface

How pairing works

These steps run in Tether Status → Pairing on the Mac. This page does not create invites, accept pasted secrets, or talk to a peer.

PAIRING COMMANDS Local handoff only

Use the exact CLI command

The browser never runs commands or reads your key store. Fill in the fields, copy the command, and run it in Tether Status → Pairing or Terminal.

  1. Create an invite on the Mac that owns the pairing

    Enter the other Mac's peer ID and choose Create. The raw secret stays in this Mac's store.

    On the Mac that owns the pairing

    Enter a peer ID and display name to build a command.

  2. Move the one-line code to the other Mac

    Use a channel you already trust — never chat, never logs. The code expires in 15 minutes and works once.

  3. Paste it on the other Mac with the same peer ID

    On the other Mac, open Tether Settings → Pairing, paste the code, and choose Import. The CLI refuses expired, reused, or wrong-peer codes.

    On the other Mac

    Enter a peer ID and one-time invite to build a command.

After import, inspect receipts with tether-fabric status --json and open the status dashboard. Same-store second import shows already used.

SETUP DIAGNOSTIC

Check your setup

Run tether doctor --json locally, then paste or drop the output below. It is parsed in this browser tab only — nothing is uploaded, and nothing here makes a network request.

Run on

Exits 1 when NOT_READY — that is expected, not an error running the command.

Up to 256 KB. Refused if it looks like a key, token, or invite — those never belong in a browser tab.

The sample is a real NOT_READY report with the home folder shortened to ~. It ships with this page, so nothing is fetched.