I open-sourced a small tool I’ve been using in my own agent workflows since March. It’s called Open Browser Operator (OBO). I know browser-agent tools are already a crowded space. I didn’t build this because I thought “an agent can click a browser” was a new idea. The thing I kept wanting was more specific: a local browser handle I could give to an agent workflow, the same way I give it a repo, a terminal, or a local server. When I’m building or operating something, the browser is often already part of the loop. I might have a local app open, a dashboard, a logged-in session, a tab group for a task, or page state I don’t want to recreate in a clean browser. OBO is my attempt to make that browser workspace addressable from agents. It runs as a local server + Chrome extension. Agents can call it through CLI / local API / skills. It can open and group tabs, read structured page state through snapshots/extraction, and use screenshots when visual context is actually needed. The part I’ve found most useful is the grouping. A tab group becomes a lightweight boundary for a task, so the agent is not just clicking random tabs in my browser. I’m posting here because I’d like feedback from people who are building agent workflows or using coding agents heavily. GitHub: https://github.com/agenthand/obo Chrome extension: https://chromewebstore.google.com/detail/open-browser-operator/mddgemobodhjojhfmdijdjgphgchcgng Install: npx @agenthand/obo submitted by /u/Smooth_Individual_62
Originally posted by u/Smooth_Individual_62 on r/ClaudeCode
You must log in or # to comment.