In part 1 of this series, we established why there is a need for a Just-In-Time (JIT) authorization system, whereby an agent has the ability to authorize itself only at the point where it is very likely that they will 1/ need that authorization and 2/ that they are clear what they will use it for. In this section, we鈥檒l look at how we have done this at Portia AI.
AI Agents are a rapidly evolving technology in the AI space. The introduction of LLMs and the ability for LLMs to interact with other software autonomously has paved the way for a new wave of technological innovation. This is an exciting development but it needs appropriate guardrails to ensure that an agent is really enacting your wishes and not sending rogue emails on your behalf to your entire address book. This is the first of a 2-part series that discusses some of the challenges of appropriately authenticating and authorizing agents so they can safely fulfill requests.
I've been tinkering with browser automation recently (e.g., building a bot to search and buy on Amazon), and Operator鈥檚 release got me thinking about the future of these tools.
Here are 3 key challenges browser agents face today:
1锔忊儯 聽 Moving from text-only to multi-modal AI models.
2锔忊儯 聽 Solving authentication without blending in with bad bots.
3锔忊儯 聽 Enabling human-in-the-loop collaboration that's seamless and smart.
In this post we unpack these challenges, share insights, and explore what鈥檚 next for browser agents. Would you trust browser agents with your day-to-day tasks? Let me know your thoughts! 馃憞