Making agent approvals easier to live with

The useful part

A guardrail becomes difficult to keep enabled when every interruption sends you looking for a phone or typing another code. I've experienced that friction using coding agents, and I've been working on the ways Doberman asks for a decision and helps you recover afterward. They solve different parts of the workflow, so it helps to know where each one applies.

How it works

• The notification goes through the ntfy server you configure, so the setup guide explains the data that leaves the machine and the self-hosting option.
• It still asks, and clicking again doesn't extend the original window.
• On a Windows laptop, Windows Hello can supply the proof for a supported two-factor action challenge.
• Once the method is available and enabled, the device verification flow can replace entering a TOTP code.
• On supported action challenges, a tap can provide the confirmation or second factor.

What to take from it

Destructive and other high-risk cases are excluded. An available Hello method ahead of ntfy can handle a two-factor challenge before the phone is used. Checking the selected method is part of setting this up, rather than assuming every installed feature is active.

Details worth keeping

There are several changes worth trying together. The approval is still tied to the action in front of you. Hello doesn't replace every password or recovery gate in Doberman.