Skip to content

User guide

Browsentic for Windows

The Windows app installs and runs Browsentic Bridge, the program on your computer that starts your agent CLI, and adds the extension to each browser from its store. It carries the same command and background process as npx browsentic@latest setup, installs them in %USERPROFILE%\.browsentic and manages them without a terminal.

7 min read Edit this page on GitHub

Requires Windows 10 or 11, on x64 or ARM64. Windows support is still experimental. On macOS, use the Mac app.


Install

In PowerShell:

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

The script downloads the latest release's installer for your computer's architecture, installs it for your user only and opens the app. It does not need administrator rights. Set $env:BROWSENTIC_VERSION = '0.8.0' to pin a release, or $env:BROWSENTIC_NO_OPEN = '1' to install without opening. The script is eighty lines, if you want to read it first.

From the installer instead

Download Browsentic-<version>-x64-setup.exe, or -arm64-setup.exe on an ARM computer, from the latest release and run it. The installer is not code-signed yet, so SmartScreen stops a downloaded copy with “Windows protected your PC”: press More info, then Run anyway. The one-line install avoids this: a file PowerShell downloads carries no mark for SmartScreen to check.

The app installs to %LOCALAPPDATA%\Browsentic, adds itself to the Start menu, and uses the WebView2 runtime that ships with Windows 11 (on Windows 10 the installer downloads it if it is missing).

The first screen: what your computer already has

The app opens on five checks and runs them automatically:

Check Passes when If it does not
This computer always Nothing to do
Node.js runtime node 20 or newer is on your PATH Install downloads the current LTS from nodejs.org into %USERPROFILE%\.browsentic\runtime\node, verified against its published SHA-256. No administrator
Browsentic Bridge %USERPROFILE%\.browsentic\cli holds the version this app carries Install copies it there, writes the browsentic.exe launcher to %USERPROFILE%\.browsentic\bin, and registers it with your browsers so they can start it
A browser Chrome, Edge, Brave, Vivaldi, Opera, Chromium or Firefox is installed Get Chrome opens the download page. Advisory: it does not block you
An AI agent One of claude, codex, agy, vibe, grok, cursor-agent, qwen, opencode or dsh is on your PATH Install Claude Code runs npm install --global @anthropic-ai/claude-code. Advisory

Set up everything installs Node and the Bridge in one click. The browser, the extension and the agent are your choice, so each has its own button. Once everything required is in place the app moves on by itself.

Claude Code on Windows also needs Git for Windows, which it runs its shell commands through.

The window

The tabs float at the top; Ctrl+1 to Ctrl+5 switch between them. Agents, Skills, Activity and Logs are pages of Settings, picked from its sidebar. Ctrl+Shift+D turns the Bridge on or off, Ctrl+Shift+R restarts it, and Ctrl+Shift+P gets a new pairing code.

Tab What you do there
Overview Turn Browsentic Bridge on and off with the power button, restart it, see its address and version. One row per browser: where its extension comes from, whether it is connected, and a button that adds it from the store. The unpacked folder sits behind Load it unpacked instead
Browsers Get a pairing code with a live countdown, see every paired browser and the store its extension came from, unpair one or all
Android (experimental) Whether a phone is ready to drive from the side panel: adb, the phone, USB debugging, Chrome, Chrome open and the screen, one row each, the same checks browsentic android prints. A row that fails says what to do, with Open Chrome on the phone, Get Chrome, the winget command that installs adb, or the page of phone makers' USB drivers, which many phones need before Windows shows them to adb. Set up your phone has the steps. The Bridge looks for phones only while this tab is open
Settings Five pages, picked from its sidebar; see below
About Who makes Browsentic, a GitHub star, every version on this computer with a copy button, Report a bug (GitHub's issue form with those versions filled in; nothing is sent until you submit it), and links to the guide, this page, troubleshooting and the release notes. Run the checks again reruns the first-run checks
Settings page What you do there
General Light, dark or system appearance for this window; whether the Bridge starts with the app; the Browser theme and Guardrails every paired browser uses, the same rows as the extension's settings page, kept in step both ways; browsentic in your terminal; the line that registers Browsentic with an MCP client; uninstall
Agents See which agent CLIs are ready, switch between them, pick a model, install a missing one, or let Browsentic fix what one still needs
Skills Every skill the router can see and which folder it came from
Activity Your standing approvals, forgettable per site, and the downloads agents captured
Logs %USERPROFILE%\.browsentic\daemon.log, followed live

The Browsentic icon in the notification area shows the Bridge's state and has the same on, off and restart controls; left-click it to open the window.

Closing the window does not stop anything. The app stays in the notification area, and the Bridge is a background process of its own, so the side panel and any MCP client keep working with the app closed or quit.

Adding the extension

Overview has one row per browser on your computer, showing where its extension came from and whether it is connected. A browser without the extension has a button (Add to Chrome, Add to Edge or Get the Firefox add-on) that opens the store page in that browser. Press the store's button, and the extension connects by itself; the row turns Connected. If it asks for a code, enter the one the app shows.

Load it unpacked instead, under the rows, is for a browser that cannot reach a store or for an unreleased build. It writes the extension to %USERPROFILE%\browsentic\extension\chrome-mv3, and Extensions in Google Chrome (or Edge, or Brave) opens chrome://extensions with that folder on the clipboard. Turn on Developer mode, press Load unpacked, click the folder picker's address bar, paste and press Enter. Reload needed shows on that row when the folder holds a newer build than the browser has loaded.

browsentic in your terminal

Settings → General → “browsentic” in your terminal adds %USERPROFILE%\.browsentic\bin to your user PATH, without administrator rights and without changing anything else in it. Terminals already open keep their old PATH, so open a new one. Every command in the CLI reference then works against the install the app manages.

browsentic.exe is a small executable rather than a .cmd script, so an MCP client, if you use one, can start it directly:

claude mcp add browsentic -- browsentic mcp

If you also installed it with npm install --global browsentic, remove that copy (npm rm -g browsentic) so two versions cannot drift apart. Settings → General warns you when it finds one.

Updating

The app checks GitHub for a newer release at launch and every few hours after. When one is out, a card appears at the top of Overview (and in Settings) with Update now, which downloads the new installer, checks that it carries a signature from Browsentic's release key, runs it and reopens the app. The app then replaces the Bridge and restarts it. Check for updates on the same card checks again immediately.

The extension downloads its updates from its store, and the side panel offers Update once one is ready. An unpacked copy needs ↻ on its card at chrome://extensions, or Update in the side panel, and the app tells you when. The extension and the Bridge do not have to be the same version.

If an update fails, nothing changes, and the card shows the PowerShell line, which installs the same release.

browsentic update does not replace an install the app made; it tells you to update from the app.

Uninstall

Settings → General → Uninstall… runs browsentic uninstall: it unpairs every browser, stops the Bridge and removes %USERPROFILE%\.browsentic and %USERPROFILE%\browsentic, optionally keeping your skills. Remove the extension from each browser first (right-click its toolbar icon → Remove). Then uninstall the app itself in Settings › Apps › Installed apps.

Uninstalling only the app from Installed apps stops the Bridge and takes browsentic off your PATH, but keeps your pairing, settings and skills, as dragging the Mac app to the Trash does.

Building it yourself

yarn win:app        # → src\windows\target\release\bundle\nsis\Browsentic_<version>_<arch>-setup.exe

This needs Node.js, Yarn and the Rust toolchain. yarn win:preview opens the window in your browser against a stand-in daemon, on any computer. The source is a Tauri app in src/windows/; see internals/windows-app.md.