Operator history and delegation for AI agents
Operator history records executive and delegation changes so an agent identity has an audit trail for who could act and when.
Why it matters
Production agents need key rotation, delegated operators, and spend authority changes. Those events should not disappear into logs.
Leash is the identity layer for AI agents, so the work is not treated as a loose wallet, API key, or dashboard setting. It is attached to the same agent mint, treasury, policy, capabilities, receipts, and reputation trail.
How Leash handles it
Leash normalizes executive registration, SPL delegation, revoke, and related events into an identity timeline with phase and transaction metadata when available.
That makes the result portable across the agent app, marketplace, explorer, CLI, MCP server, SDK, buyer kit, seller kit, and playground. The surface can change, but the identity and proof trail stay the same.
Implementation checklist
Record who owns the identity, who operates it, which token approvals exist, and whether each event was prepared, submitted, confirmed, or failed.
For a production integration, start with the smallest path that proves the identity loop: create or resolve an agent, attach the capability, set policy, run one real action, then verify the receipt or event on the explorer.
Inspect delegation from the CLI
leash agent show
leash treasury limit --token USDC
leash treasury set-limit --token USDC --revokeFAQ
Why split owner and executive roles?
The owner can keep custody while the executive operates online with limited delegated authority.
Does operator history expose private owner data?
Public views should show only public, confirmed operator and delegation events. Owner views can show more detail.