browsentic Files

Features

• apps: the Mac and Windows apps add the extension from each browser's store — one row per browser with its store, its version and whether it is connected, a button that opens the store page in that browser and shows the code to enter, the unpacked folder behind "Load it unpacked instead" and asked for ↻ only there; entry no longer waits on an unpacked folder, installing the Bridge registers it with every browser, Firefox is detected, and the apps call the computer half Browsentic Bridge (cfb88b6)
• setup: ask which browser, open its store page in it, and wait for it to pair — Chrome, Brave, Arc, Vivaldi, Opera and Chromium from the Chrome Web Store, Edge from it too until Edge Add-ons publishes, Firefox the signed add-on, the unpacked folder only when asked for; with no terminal it prints the plan instead of asking, "browsentic browsers" lists them for the apps, status shows each paired browser and its store, and uninstall from an app no longer crashes on a constant read before it was set (48f12b7)
• bridge: take any extension at protocol 22 or newer, let both store copies start the Bridge, and keep three pairing codes live — a store copy a version ahead is welcomed and proves itself at its own number, an older one is refused in words it already reads, and each session says which store it came from (2e387e2)
• agents: Cursor CLI reaches the browser — each turn approves its own MCP server, an approval outlasts its 60-second calls, a result fits what it passes on, and a call any agent abandons withdraws its approval (728835e)
• agent: SITE_BLOCKED tells the side-panel agent and MCP clients the user has put a site off-limits — stop and say so, never retry it or reach it another way (31fb362)
• extension: blocked sites — a list of sites Browsentic will not read or act on, kept in this browser only and enforced in the extension before any tool runs, so neither the daemon nor the agent it spawns can see or loosen it (#53) (00a459c)
• an About page in the extension's settings and an About tab in the Mac and Windows apps — the author, a GitHub star, every version with a bug report that fills them in, and the guide, troubleshooting and release notes (fa19e95)

Fixes

• windows: draw the unpacked section with classes the frozen extension's stylesheet already has — Tailwind scans the whole repository, so pl-4, rotate-90 and text-[12px] had reached the extension's CSS and broken the store lock (921feb2)

Documentation

• install from the stores — the extension from the Chrome Web Store (Edge too until its listing is out) or the signed Firefox add-on, Browsentic Bridge from the apps or npx, a code entered once; the window that lets the two differ in version, store listings and what each dashboard asks for, the README's three steps with store badges, the npm page, release notes and app screenshots (959702b)
• approvals: a card the agent stops waiting for comes down, and a late answer runs nothing; on Cursor CLI an unanswered card is asked for again after a minute (7e0e587)
• agents: Cursor CLI as measured — the per-turn approval, the tool lookup, the 60-second call, the 40,000-byte result and the plugin servers (e7b4b5c)
• blocked sites — writing a pattern, what it stops, why nothing on the daemon's side can override it, SITE_BLOCKED, and where the list lives (ea21bf6)

Chores

• extension: lock the extension to the v0.8.0 build the stores are reviewing — store-lock.json lists every file of it, and CI and the release fail on any change until a new store submission rewrites it (7a7b30c)
• license: Browsentic is licensed under Apache 2.0 instead of MIT — both LICENSE files, the package fields, the READMEs, CONTRIBUTING and SECURITY, the About pages in the extension and both apps, and the apps' copyright lines; versions up to 0.7.15 stay MIT (966adaa)

Install

Browsentic is two pieces plus the AI you already use. Install the first two in either order, then pair them once with a code.

1. The extension, in your browser:

• Chrome, Edge, Brave, Arc, Vivaldi, Opera — Chrome Web Store. In Edge, press Allow extensions from other stores first. It updates itself.
• Firefox 140 or newer — browsentic-0.8.0-firefox.xpi below, signed by Mozilla. Open it in Firefox and accept both prompts; it updates itself.

2. Browsentic Bridge, on your computer. It runs your agent and keeps everything local.

macOS — installs the app, and the app installs everything else, Node included:

:::sh
curl -fsSL https://browsentic.com/install.sh | sh

The Browsentic-0.8.0.dmg below is the same app. It is not notarized yet, so a downloaded copy is blocked on first open: System Settings → Privacy & Security → Open Anyway. The line above avoids that.

Windows 10 or 11 (experimental) — installs the app, and the app installs everything else, Node included:

:::powershell
irm https://browsentic.com/install.ps1 | iex

The Browsentic-0.8.0-x64-setup.exe and -arm64-setup.exe below are the same app. They are not code-signed yet, so SmartScreen warns on a downloaded copy: More info → Run anyway. The line above avoids that.

Any platform — macOS, Windows or Linux, with Node.js 20 or newer:

:::sh
npx browsentic@0.8.0 setup

It asks which browser should get the extension, opens its store page there, and prints a pairing code. The apps do the same from their Overview tab.

3. An agent CLI you are signed in to — Claude Code, Codex, or another supported one.

Then click Browsentic in the toolbar and enter the pairing code, once.

Already running an older version? The Mac and Windows apps offer the update on their Overview tab, and npx browsentic@latest update updates the Bridge from a terminal. Your browser stays paired, and the extension and the Bridge do not have to be the same version. Only an unpacked copy needs ↻ on its card.

Full changelog: https://github.com/imshaikot/browsentic/compare/v0.7.15...v0.8.0