QR Approval is the mobile signing path for approvals that need to happen now. The page (Slack message, email, PagerDuty alert) carries a QR. Scan with your phone camera. Review the diff, blast, and rollback plan. Sign with your fingerprint. The action commits. The whole loop usually takes under 15 seconds.
Every QR carries a single-use signed token. The token is bound to the request id, the approver's user id, and a 5-minute window. After scanning, the token is consumed; replaying it (from a screenshot, a forwarded message, anywhere) does not work. Replay Guard guarantees this. Nobody has to worry about screenshotting an approval QR for context.
Signing requires a biometric (fingerprint or Face ID) on the phone. No passwords typed at 3am. The biometric prompt comes from the phone OS, not from a Nova-controlled UI, so platform-level security guarantees apply. The signature is a WebAuthn credential signed by the phone's secure enclave.
After scanning, the phone shows the same review surface as the desktop Approval Queue: the proposed diff, the blast radius, the rollback plan, the agent's reasoning. Sign only after the review. The page is designed to look the same on phone and desktop so a partial review on one finishes naturally on the other.
Every QR scan is logged: scanned, expired, replayed, rejected, signed. The Decision Bundle for the action carries the QR audit row directly so the post-incident review sees the full mobile flow without a separate query. Lost-device events (a phone marked deauthorized) are also logged so audit can verify nothing was approved from a stolen device.
Subscribe to Nova AI Ops on YouTube for demos, tutorials, and feature deep-dives.
A 3am critical request should not require booting a workstation. QR Approval makes the response time match the urgency.