Type · 8 pieces
Articles on AI agent authorization
Analysis and engineering notes on how AI agents get authority, how they lose it, and how task-scoped warrants bound what an agent can do.
Agents are insiders. Insiders delegate.
Microsoft says AI agents should receive only the authority their task needs. A warrant chain keeps that limit intact when one agent delegates to another.
Read article →Personal agents that both sides can trust
Personal agents now sign in via PACT and PAP. Task-scoped warrants add the customer's own terms, checked at the API, with receipts both sides can verify.
Read article →Most companies have an AI policy. Very few can enforce it.
87% of IT leaders say an AI agent reached data it shouldn't have. Why written AI policy breaks down at runtime, and how per-task warrants enforce it.
Read article →Let Authority Follow the Work: Tenuo for NVIDIA OpenShell
How NVIDIA OpenShell and Tenuo combine secure execution with task-scoped authority that can move across tools, sandboxes, and agent handoffs.
Read article →Give your agent a valet key
SalesBleed leaked Agentforce CRM data without breaking an authorization check. Why AI agents need task-scoped authority, with a runnable Tenuo example.
Read article →Per-request authorization for Temporal Nexus
Nexus allowlists decide whether a namespace may reach an endpoint. They cannot evaluate the request. Here is how task-scoped warrants close that gap without changing service contracts.
Read article →Task-scoped authorization for durable AI workflows
How Tenuo and Temporal combine durable execution with task-scoped cryptographic authorization.
Read article →Your AI agent is authorized to do everything wrong
Why identity-based authorization fails when agents act autonomously, and what warrant-based authorization looks like.
Read article →