Background workers are great until the agent is about to submit something under your name. That is the line where automation changes character. For low-risk work, the best interface is often no interface. Let the agent classify the lead, summarize the page, enrich the record, monitor the inbox, or draft the first pass. If the action is reversible, internal, and easy to inspect later, hiding the machinery is a feature. But a different kind of workflow is arriving: agents that apply for jobs, publish content, issue refunds, update customer records, book travel, send replies, change dashboards, and operate logged-in web apps. Those are not just browser tasks. They are trust-sensitive actions. The product problem is not removing every bit of friction. It is deciding where friction belongs. The browser is where authority lives Agents want browsers because the browser is where work already happens. APIs are incomplete. Internal tools are inconsistent. OAuth scopes are often too coarse.…