Media
3 items
Description
Your real Chrome, open for any AI agent. Reuse your logins instead of automating a blank remote browser. our browser, open for any AI. BrowserMan lets any AI agent drive your real Chrome — with your sessions, cookies, and tabs — while your credentials stay on your device. It works with local agents, cloud agents, and scheduled tasks, through MCP or a plain HTTP API. Local tools like Browser MCP and Playwright can see your logins, but the agent has to live on the same machine. Cloud browsers like Browserbase can be reached from anywhere, but they can't see your logged-in sessions. BrowserMan is the bridge: real logins + agents anywhere + cookies that never leave your device. WHAT YOU CAN DO • Automate any website with the core browser tools (navigate, read, click, type, scroll, screenshot, upload). If you can do it by hand, your agent can do it too. • Delegate scoped access per agent or per vendor, audit what each one did, and revoke in one click from the dashboard. BUILT FOR AGENTS, NOT FOR SCRIPT-WATCHERS If you have ever driven Playwright with an LLM, you know the loop — HTML dumps, selector guessing, flaky retries. BrowserMan was built the other way around: • Agents read a numbered accessibility tree, not raw HTML. Prompts are roughly 15× smaller. • Each platform action is one typed call, not a 20-step fragile chain. • Tabs are reused, grouped into a single BrowserMan tab group, and cleaned up automatically. PRIVACY-FIRST BY DESIGN • Page content, cookies, and credentials never leave your browser. • The BrowserMan server is a thin relay — it carries command envelopes, not page data. Command results are streamed to your agent and not retained on the server. • Session tokens and API keys are stored only as SHA-256 hashes. • Every action is logged against the agent or key that made it, so you can answer "who did that?" in seconds. • Open source, self-hostable, and free to use at browserman.run. HOW IT WORKS 1. Install the extension (this page). 2. Sign in and pair your browser from the side panel. 3. Approve your AI agent from the terminal or web, and point your MCP / HTTP client at BrowserMan. The dashboard at browserman.run lets you name browsers, scope delegated access per agent, see recent executions, and revoke anything on one click. LINKS • Website: https://browserman.run • Privacy policy: https://browserman.run/privacy • Recipes (pre-built script catalog): https://browserman.run/recipes