@TelegramSam Great scenario! This is exactly what we’ve been envisioning for Sovrin login—which, as you say, doesn’t really feel like “login” any more, since it’s really about connection between two peers.
@phil 100% agree that the agent is separate from the browser so that you can use any browser. Ideally where we are going is what I call agent-aware browsers. Today, browsers know how to deal with: a) websites, and b) plug-ins or extensions. The websites are remote, in a different security and privacy domain, and interact a standard protocol like HTTP/S. The plug-ins are local, in the browser’s own security and privacy domain, and interact with using the extension’s local APIs.
I see agents becoming the third type of entity that browsers know how to deal with—an entity that is a hybrid of the other two because: a) the browser speaks to the agent via a standard protocol much like it speaks to a website, BUT b) unlike a website, the agent operates within the security and privacy perimeter of the browser (i.e., it is trusted by the user), and c) the agent exposes a set of API extensions that can do much more than the API extension (plug-ins) that live only in the browser.