Dualkey Agent

DualKey

[](https://github.com/wadeKeith/dualkey-agent/actions/workflows/ci.yml) [](https://github.com/wadeKeith/dualkey-agent/releases) [](./LICENSE) [](./pyproject.toml)

No dangerous agent action without a second key.

Add approvals, policy, and receipts to any AI agent in 10 lines.

DualKey is an execution authorization layer for AI agents. It sits between an agent deciding to do something and that action actually running. The goal is simple: standardize risky actions, evaluate them with deterministic policy, require a second key when needed, and leave behind tamper-evident receipts.

Demos

GIFs are still being recorded. The cards below mark the three public-facing demos the repo is built around:

Coding agent approval	Browser checkout approval	MCP tool governance
		

Why this exists

The agent ecosystem already has plenty of planning and orchestration. What it still lacks is a shared control plane for dangerous actions:

• browser-use can click through checkout flows.
• coding agents can edit files, run shell commands, and push branches.
• MCP servers expose tools that can reach secrets, production systems, and real money.

DualKey focuses on the missing layer:

• action normalization
• deterministic policy
• approval / denial
• evidence receipts
• replay-ready event history

DualKey vs frameworks

| Question | Agent frameworks / runt