Engineering preview Diagnostic stays on this machine SSH or the Mac app

How pairing works

Run tether pair <ssh-host> on the machine where you want to borrow capacity. Use a Mac, Windows, or Linux machine you are authorized to connect to over SSH. The invite form below is the Mac app's alternative pairing route; this page never runs commands or handles your key store.

ADD A MACHINE Local handoff only

Connect a donor over SSH

On the machine where you want to borrow capacity, enter the SSH destination for a Mac, Windows, or Linux donor you are authorized to use. Tether checks it before installing or pairing anything.

Enter an SSH destination to build a command.

Next: run tether doctor to see what still needs measuring, then tether --auto -- <command> for a supported job.

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. Alternative: create an invite for the Mac app

    Use this when the donor has the Tether Status app and cannot be connected to with tether pair <ssh-host>. The raw secret stays in the pairing machine's store.

    On the Mac that owns the pairing

    Enter a donor 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 donor ID

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

    On the other Mac

    Enter a donor 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.