Approve what matters from your phone.
ACT turns risky agent actions into clear approval requests. When an agent wants to do something big, like submitting a form or rebooting a server, the request lands on your phone first. You approve, modify, or deny. Then, and only then, the action runs.
The flow
From request to recorded action.
A request comes in and you review it. If you approve, a signed clearance is issued. The action uses it once, and everything is recorded.
- Prompt
- Plan
- Approval
- Action
- Audit
Agent requests permission to submit a browser form
Medium- Action
- Submit appointment form
- Scope
- clinics.example only
- Expires
- 5 minutes
Approved · clearance issued
Single-use clearance consumed by BrowserBridge
Requests route from every surface
- Browser submission
- KVM reboot
- Hermes workflow
- MCP tool action
Audit trail, written as it happens
- 12:04:09Request received from BrowserBridge
- 12:04:15Approved by you · single-use clearance issued
- 12:04:17Clearance consumed · form submitted · task complete
The real app
This is ACT, not a concept render.
Screenshots from the ACT app running with a demo workspace: the tower dashboard, an approval with its redacted payload, and the agent fleet.
Under the hood
Simple on the surface. Strict underneath.
- Consequential actions
- Submitting a form, rebooting a machine, running a workflow: anything with real-world effect pauses for you.
- Human approval
- Requests arrive as plain-English cards. Approve, modify, or deny in one tap.
- Signed decisions
- Your approval is signed on your device, so the requesting product can verify it really came from you.
- Clearance consumption
- Each clearance is single-use and scoped. It works for the action it was issued for, then it's spent.
- Audit history
- Every request, decision, and action is recorded, so you can always see what happened and why.
- Your approval device
- ACT runs on iOS and Android. Approvals are signed on your phone, backed by its secure hardware.Get started on GitHub →