you@your-mac — pairling — 80×24

Last login: Wed Jul 2 23:18:44 on ttys001

you@your-mac ~ %

Why Pairling

See everything

01 / 03

The product story, full list

    Capabilities, full list

      Capabilities

      One connected system

      The terminal on the left runs on your Mac. The e-ink phone on the right just rode the encrypted route in and docked as the live controller. They are the same product, joined by a private Pairling Connect line.

      pairling — capabilities
      capabilities 4

      Every project, sorted.

        Attention

        Put it down.
        It taps you.

        Pairling alerts you when a turn completes, an approval waits, route health changes, or a worker looks stuck. Every notification routes you back into the right session.

        • Live Activity on the Lock ScreenThe current turn's phase, elapsed time and token flow stay glanceable without unlocking.
        • Dynamic IslandCompact state while you are in other apps. Expand for the active tool and session.
        • Push that routes you backCompleted turns, waiting approvals, route risk and worker pressure deep-link into the right session.
        • Apple WatchMac status, the active session and a sentinel snooze from your wrist.
        Trust

        Know what it can reach.

        Control stays scoped to the session you pick: iPhone to Pairling Connect, then to the paired macOS environment and the CLI session you chose. Nothing else on the machine is in reach.

        iPhone app→ Pairling Connect→ paired Mac→ CLI session

        The perimeter is a named, documented surface: the Agent Control Protocol. Every endpoint the phone can reach, exactly as enforced. Not promised — enforced in code.

        Keychain-scoped pairing

        Pairing is scoped to one Mac, and the credentials live in the iPhone's Keychain.

        No hosted transcript store

        By default, transcripts stay in the paired environment. There is no Pairling cloud copy and no Pairling account.

        Selected-session controls

        Commands target the session and provider you choose, with action receipts showing what was applied.

        On-device redaction

        Sensitive strings are stripped on the iPhone before any assist leaves it. This path never falls back to a network model.

        A private path, not a hosted relay

        Pairling Connect runs a WireGuard-encrypted tailnet node inside the app. No separate VPN app, no system VPN profile. The relay is only an App Attest-gated fallback.

        The Agent Control Protocol

        The phone can only reach the session endpoints you granted. The perimeter is documented endpoint by endpoint and enforced in the Connect bridge.

        FAQ

        The questions we would ask too.

        pairling — faq