Questions people actually ask
Short answers. Where the honest answer is "no" or "not yet", it says so.
Partly. Approvals and the chat transcript both come from Claude Code — approvals through its hook system, the conversation from the transcript files the daemon tails — so both are Claude Code only today. The Sessions list and the SSH terminal work with anything running in herdr, tmux or zellij, and live pane status is read for Claude Code and Codex. Hook-based approvals for other agents come as they expose a pre-execution hook.
No. There is nothing to sign up for. The early-builds list takes an email to send you a build link, and that's the only thing we ever ask for.
Yes. Put both devices on Tailscale (or any VPN that gives your machine a stable address) before you pair — the QR records every route it can see, and the app probes them and moves the session to whichever answers, so Wi-Fi to cellular roaming needs no action from you. That provider is then in your network path — Reins itself still adds no third party.
Because there's no server to send them. Push notifications need a service holding a token for your phone; Reins doesn't have one. Alerts arrive while the app is open or backgrounded. On iOS a pending approval also shows as a Live Activity on the lock screen.
After 60 seconds (configurable) the phone's window closes and Claude Code shows the permission prompt at your desk, exactly as if Reins weren't installed. An unanswered approval is never a denial — if you want it blocked, tap Deny.
Yes — replying from the phone works by typing into the terminal your agent runs in, so a paired phone is as privileged as a shell. Pair only your own devices, revoke a lost phone from Machine, and if you want watch-and-approve only, run the daemon with --allow-chat-send=false.
Only for replying and answering questions. A bare terminal has no API for injecting keystrokes; a multiplexer does. Replying works with any of the three; answering a question card needs herdr, whose socket API the app drives directly. Approvals, the live feed and the SSH terminal work regardless.
Not yet. The protocol carries hostnames, the app stores one pairing. Multi-host is the next big piece.
Nothing. No analytics, no crash reporting, no telemetry, no relay. You can verify this yourself in two minutes — the Security page has the commands.
Camera to scan the pairing QR, photo library for attaching a screenshot, microphone and speech recognition for dictation, and local network to find your machine on the pairing screen. Each maps to one feature and each is optional — decline them all and approvals, chat and the terminal still work.
The pairing — host, token and SSH key — in the phone's keychain, plus a capped cache of recent sessions, commands and decisions so history survives a restart. Revoke clears the pairing; it does not clear that cache. Deleting the app removes both.
Not yet. The install script and the signed binaries are public, with SHA-256 sums you can check against the release. The source isn't published — so until it is, trust the daemon on what you can verify from the outside: the commands on the Security page show you everything it listens on and every connection it makes.
Not as a host. The daemon needs a Unix socket and sshd; WSL2 works if you run the daemon inside it and SSH into WSL. The phone app runs on iPhone and Android.