A browser agent that can read a support ticket is useful. A browser agent that can refund $4,500 without approval is a production incident. That distinction is where most browser-agent demos stop being demos and start becoming systems. The click loop is getting good. Agents can open pages, read tables, fill forms, use tools, and drive real browsers. Some run in cloud browsers. Some run locally. Some are arriving as Chrome extensions with per-site permissions. The interface is improving quickly. But production risk does not start at the click. It starts when the click has write authority. Refunding a customer, deleting a CRM record, publishing a post, exporting a list, changing account settings, sending a customer-facing email, charging a card — these are not the same kind of action as reading a dashboard. They cross the write boundary. For high-value browser actions, logs are too late. Logs explain. Gates prevent. Receipts and audit logs are necessary.…