Your agent has a valid credential.
delego makes sure it’s doing the right thing.
Deterministic, per-action authorization bound to the human’s instruction. Approvals a prompt injection can’t re-point. No LLM in the path. Rides your broker; doesn’t replace it.
Auth was built for humans and static apps.
Agents broke the model.
Agents act on your behalf and autonomously. Login-and-scopes was never built for software that takes actions — and a credential can’t catch a redirected one.
order {amount:2400, destination:internal} → fpr c70d4ee5… approved
order {…, recipient:"attacker"} → fpr dabddc8f… deny
One decision point. Every action accounted for.
The agent proposes; delego decides — deterministically, no model in the path. Sensitive actions park for a human. Every decision gets a signed receipt.
Add authorization and a signed audit in a few lines.
One small, deterministic, Apache-2.0 library. No LLM in the path, no credential custody — it rides your broker instead of replacing it.
# first match wins · fail-closed rules: - name: place-order decision: needs_approval match: { method: POST, path: /orders } constraints: amount: { field: amount, max: 5000, currency: USD } allow_list: { field: destination, in: [internal] } default: deny # anything not allowed is refused
A signed receipt for every access and every action.
Who did what, when, and under whose authority — a hash-chained ledger you verify and export as compliance evidence. Anchor the chain head externally and verification also proves nothing was rolled back.
One deterministic core. A toolkit around it.
The core ships today: a library, a CLI, and an MCP server — plus Claude Code agents and skills to operate it. Brokering and identity are next.
Initialize delego, draft and inspect policy, work the approval queue, and verify the signed audit chain — from your terminal.
pip install delegoA FastMCP server exposing propose · resolve · audit tools, so any agent — Claude or any MCP client — routes its actions through delego.
View on GitHubClaude Code subagents that adversarially review your policy and broker adapter, and hunt the ledger for anomalies.
View on GitHubClaude Code skills to set up delego, draft policy, triage approvals, and read the audit trail in plain language.
View on GitHubA first-party credential broker: the secret is injected only after authorization, never entering the agent’s context.
Identity for humans and agents — sessions, OAuth/SSO, passkeys, and first-class agent principals with scoped, revocable credentials.
Put delego in front of your agent.
Authorize every action your agent takes — one command with the Claude Code plugin, or a Python library and MCP server in your app.
# one command in Claude Code — skills, review agents & the MCP server /plugin marketplace add Delego-Dev/plugin /plugin install delego@delego # initialize the delego home (signing keys + example policy) and verify /delego:init
# install the library (+ the optional MCP server extra) pip install "delego[mcp]" # initialize the home (signing keys + example policy) delego --home .claude/.delego init # see it work — allow, deny, over-cap, approval, the confused-deputy refusal python examples/demo.py
Building UI too? The @delego shadcn registry ships the decision pill, signed receipt, and theme.
Open source today. Hosted control plane next.
The core, CLI, MCP server, and spec are open source forever. A hosted authorizer, approval queue, and dashboard are coming.
- Deterministic policy engine
- Signed, hash-chained audit
- CLI + MCP server
- Apache-2.0
- Hosted PDP & approval queue
- Web approvals & dashboard
- Exports & retention
- SSO for your team
- HSM / KMS signing keys
- External head anchoring
- Compliance evidence exports
- SLA & support