Attended confirmation
kovra confirm exposes kovra’s approval broker as a standalone primitive. It
asks a human to bioProve a described action and exits 0 if approved, non-zero if
denied or timed out — so any trusted app or script can gate its own action behind
a real human, the same way a secret reveal is gated.
It is secret-independent: it needs no vault and no master key. It just opens the broker, shows your description as the authoritative prompt, and reports the verdict through its exit code.
~ % kovra confirm "Promote build 1.2.3 to staging"Approval required: Promote build 1.2.3 to stagingApprove at the biometric prompt, or (file broker) run `kovra approve --list` then `kovra approve <id>` in another terminal. Waiting…Approved.Windows — coming soon. The same model on Windows Hello + Credential Manager.
Gate your own action
Section titled “Gate your own action”Because the verdict is an exit code, wiring it into a script is one line:
if kovra confirm "Deploy to production"; then ./deploy.shelse echo "Denied — not deploying."fi--ttl <seconds> bounds how long it waits before failing safe to a denial
(default 120s).