Reins

Guides

One task each, in the order most people do them. Every step is what the daemon and the app do today; the docs hold the full reference.

  1. Approve Claude Code permission prompts from your phone

    Put every Claude Code permission prompt on your phone, with the command or diff: install the Reins daemon, run setup, scan the QR, hold to approve a force-push.

  2. Claude Code notifications on your phone, with Reins

    Know on your phone when Claude Code needs you or finishes a turn: the hooks Reins installs, how the Android wake-up push works, and what an iPhone shows today.

  3. Approve Cursor agent commands from your phone with Reins

    Wire Reins into Cursor so its agent asks your phone before it runs a command or edits a file: the hooks.json it writes, a dry run, and what the Inbox shows.

  4. OpenCode permission prompts on your phone, with Reins

    Reins installs an OpenCode plugin that sends each permission request to your phone and posts your answer back: setup, once or reject only, and OmO.

  5. Approve agents away from home: Reins over Tailscale

    Reins connects your phone to your machine, so away from your network it needs a route. Put both on Tailscale, check reins routes, and keep approvals coming.

  6. Run Claude Code from your phone: a terminal that lasts

    Open a shell on your machine from the Reins app, type to a running Claude Code session, and come back to the same shell after a drop: herdr, tmux and zellij.