Your customer logs in, and you know who they are. But increasingly, the person on the other end isn't typing. They've asked an AI agent to book the trip, reorder groceries, or check the claim. Most apps handle this badly: either the agent borrows the customer's credentials and becomes invisible, or it gets blocked and takes the customer's business with it. What if your app could tell the difference and respond appropriately?
That is the idea behind session delegation. The session still belongs to the customer, but it also names an actor: the agent acting on their behalf. Because the actor is explicit, every action can be traced to the right party. You can apply authorization policies written for agents, such as allowing a reorder but requiring approval for a payment. You can also handle these sessions differently, with shorter lifetimes, stricter flows, and revocation that leaves the customer's own access untouched.
We'll explore the concept in a live environment, and look at how emerging approaches such as the Personal Agent Protocol (Poppy) frame the same problem.
