Pair with the Console

The Console is loopkeep's web control plane: sign in, see your paired devices, revoke a stolen one, and connect GitHub and Slack so their events can trigger workflows on your machine. Pairing is optional — everything local (cron, file watching, git triggers, the inbox) works without an account, forever.

Pair this device

Open the desktop app and follow the sign-in prompt — it walks you through pairing when you first launch it. Your browser opens an approval screen; approve it and the app finishes the pairing. The device gets its own token and signing key; nothing is shared between devices.

Prefer the terminal? The CLI runs the same flow — like claude or gh:

lk login

Afterwards:

lk account    # show login state and the Console connection
lk logout     # revoke this device and log out

Manage devices

Open the Console and go to Devices. Every paired device is listed, and any of them can be revoked from there. Revoking invalidates the device's token — useful when a laptop is lost or stolen. There is deliberately no remote kill switch for the runtime itself: revoking a device cuts its Console connection, it does not stop workflows on the machine. Protecting a lost machine's disk is the job of OS disk encryption.

What pairing enables

• GitHub and Slack triggers — events are delivered to your daemon as wake signals through the Console. See The Console for how this works and what the Console can and cannot see.
• Remote revoke — unpair a device from the browser.

What stays on your machine

The daemon connects outward to the Console over WebSocket — no inbound ports are opened. Wake signals carry no content: when a GitHub or Slack event fires, the daemon fetches the actual data from the source API with its own credentials. Your code, secrets, and event log stay home.