Skip to the content

Approve risky actions on Windows

Enrol a security key on a Windows PC and approve each command your policy asks about through Windows' own WebAuthn; Windows Hello itself comes later.

Built, not yet claimed preview: this guide describes a package that has not passed its release gate.

Enrol a FIDO2 security key on a Windows PC through Windows' own WebAuthn, keep the presence watcher running, and approve each command your policy asks about with the key's PIN and a touch: the watcher shows exactly what will run, the approval is good for that one call, and nothing the agent does on its own can give it. Windows Hello, the PC's built-in fingerprint, face or PIN, is built the same way but stays switched off until its isolation is proven on a real Windows 11 device.

1. Know why Windows Hello is switched off for now

A Windows Hello key belongs to your Windows account, so any program running as you could ask for a signature with it, including an agent. AgentGarm uses Hello only from inside its own packaged helper, agentgarm-agent, which runs in an AppContainer under the AgentGarm.Agent package identity, and agentgarmd accepts a Hello key or approval only from that package, signed by AgentGarm and started from C:\Program Files\AgentGarm\bin. That is built, but turning it on waits for a test on a real Windows 11 device that a program outside the package cannot use the key. Until then agentgarmd refuses Hello keys, agentgarm enrol --method hello is refused, and Windows approvals use a FIDO2 security key.

Windows Server and Remote Desktop sessions always need a security key, redirected over Remote Desktop or plugged in, with no software fallback. Approvals need the Windows service install, where agentgarmd runs as SYSTEM; without it every approval is only the agent's own prompt.

See also

Run AgentGarm on Windows

Install the Windows preview, start agents in its Job Object sandbox, use the tray, know what Windows enforces next to macOS and Linux, and remove it.

2. Enrol a security key

In your own terminal, whoami /user prints your SID. An administrator, in an elevated terminal, opens a 5-minute enrolment window for it with agentgarm enrol --open; the window admits one key, and agentgarmd refuses to open one from inside a governed task. Then, as yourself in an ordinary terminal (not elevated), run agentgarm enrol. Windows asks for the key's PIN and a touch, and agentgarmd checks that the key verified you before it binds the key to your account and records the enrolment in the audit log.

On a PC enrolled in Central Lite, an administrator can issue you a presence enrolment grant instead of opening the window as administrator (enrol developer machines).

agentgarm enrol --open <user SID>
agentgarm enrol

3. Keep the presence watcher running

agentgarm presence watch receives your approval requests one at a time. Start it in a terminal of your own, outside any agent, in your desktop session: it exits at once in a service session, without the service install, or while you have no key enrolled. agentgarm doctor's presence line says whether agentgarmd has a key enrolled for you, has revoked it, or has none, and whether Windows Hello is available or still switched off.

agentgarm presence watch
agentgarm doctor

4. Read the request and approve, or refuse

When the policy asks about a call, the hook denies it for now and tells the agent to wait for your approval and retry. The watcher prints “approve for AgentGarm:” with the command exactly as it will run, secrets replaced, and how many seconds you have. Enter the key's PIN and touch it to approve: the watcher prints approved:, and the agent's retry of exactly that call, in that task, is allowed once and recorded with the approval. Cancel Windows' prompt, or do nothing until the request expires, and the call stays denied.

The signature covers this one request in your own Windows session, so it cannot be replayed, moved to another command or answered from another session. For agents started with agentgarm run, whose sandbox keeps them away from the key, approvals rate B; hooks-only sessions rate C.

See also

Approve risky actions with Touch ID

Enrol a Touch ID key on your Mac and approve each command your policy asks about with your fingerprint, for that one call only.

5. Re-enrol when a key stops working

agentgarmd revokes a security key whose signature counter does not rise, and the watcher stops. Once Windows Hello is on, clearing the PC's TPM or resetting your Windows Hello PIN invalidates a Hello key: the watcher reports which one happened, and agentgarmd revokes the key and raises an alert. Either way, every ask is denied until you re-enrol, with a new window from an administrator, and start the watcher again.

agentgarm enrol --open <user SID>   # an administrator, in an elevated terminal
agentgarm enrol                     # you, within 5 minutes
agentgarm presence watch

6. Require presence on a rule

The same policy works on Windows as on a Mac or Linux. Add presence: required to an ask rule when the agent's own prompt must never answer it: with no key enrolled for you, or a revoked one, agentgarmd turns that ask into a deny, and the reason says how to enrol. The Touch ID guide shows the rule.

See also

Approve risky actions with Touch ID

Enrol a Touch ID key on your Mac and approve each command your policy asks about with your fingerprint, for that one call only.