The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Browsentic listing page.
https://github.com/user-attachments/assets/307afa62-5fbd-47ac-822c-baee491ddfe3
No account · No auth · No API key · No cloud · No telemetry · Local first
Your real, logged-in browser, driven from an AI side panel by the agent CLI you already have.
Also an optional MCP server, so any MCP client can drive the same browser.
Any platform — with Node.js 20 or newer (Windows is experimental):
macOS — one line installs Browsentic.app, which brings Node and everything else:
Windows — one line in PowerShell installs the Windows app, which brings Node and everything else (experimental):
Full install and setup guide, Firefox included: browsentic.com/docs/guide/install

The extension dials out to the daemon, because a Manifest V3 service worker cannot listen for connections. One daemon owns the browser link, so several MCP clients can share one browser. Everything binds to 127.0.0.1.
Nothing connects until you pair, both ends prove themselves, consequential actions ask first, and credentials on a page are sealed before the agent sees them. The full model is in SECURITY.md, and what it does not cover is in Limits.
Bugs and ideas are welcome — start at CONTRIBUTING.md.
Browsentic is MIT licensed.
Short answer: "Browse" + "agentic".
Long answer: Most browser automation asks you to hand the work to a different browser — a headless one, in a container, logged in to nothing. Browsentic is the other way round: the agentic part happens in the browser you are already looking at, with the sessions you are already signed in to. The name is the thesis — browsing, made agentic, where you already browse.