Penut Operator

Penut Operator lets approved Penut browser actions run in your own logged-in Chrome profile. Data disclosure: Before pairing, Penut shows a disclosure and asks for consent. Pairing stores a generated device ID, the device name "Browser," a pairing token, connection status, and audit records for approved browser actions. When an approved action runs, Operator may send page observations, screenshots, execution events, and results back to Penut so the approved action can be completed and reviewed. Penut Operator does not collect your browsing history. Use it when a workflow needs the browser state that only exists on your machine, such as an already signed-in website session. Penut queues the action after approval, sends it to this extension, and records execution status back in Penut. The extension connects only to Penut, runs only approved browser playbooks, and uses Chrome debugging permission so it can navigate, inspect pages, and complete the approved action in the active browser profile.