browsentic Files

Browsentic now runs on Windows, with an app that installs it in one PowerShell line. It also runs a task on a schedule, listens hands-free, keeps its settings on a page of its own shared with the Mac app, and runs Codex through its app-server. 0.7.7 to 0.7.10 were never published on their own, so this release carries all five steps, newest first.

The extension and the daemon speak a new protocol (21), so update both together: npx browsentic update, then ↻ on the Browsentic card. The Mac app does both from its Overview tab.

The extension asks for two new permissions: nativeMessaging, so a browser can start the daemon when it is down, and offscreen, which hands-free mode listens through (Chromium only). Firefox may hold the signed update until you accept the new permission.

0.7.11 · Windows, with an app of its own (experimental)

• One PowerShell line installs the Windows app: irm https://browsentic.com/install.ps1 | iex. It is the Mac app's twin: a first screen that installs Node.js (from nodejs.org, checked against its published SHA-256), the command and the extension in one press, then the same seven tabs, an icon in the notification area and an updater. Per user, no administrator, on x64 and ARM64 (#47)
• browsentic in any terminal, from the app's Settings tab. It is a small browsentic.exe, not a script, so an MCP client starts it directly: claude mcp add browsentic -- browsentic mcp (#47)
• Six of the eight agents were refused on every Windows run. The folder check read only / paths, so every agent but Claude Code and Codex failed as AGENT_UNSAFE. It now follows the platform's own path rules, and refuses a .. that climbs out of the state folder everywhere (#46)
• Agents installed with npm start on Windows. Their .cmd shims are read and the program they name is started directly, never through cmd.exe, with no console window, and a cancel ends the agent with everything it started (#46)
• Claude Code gets its message on stdin and its prompt from a file, so no turn outgrows Windows' 32,767-character command line. On macOS and Linux this also keeps page text out of ps (#46)
• The unpacked extension can wake the daemon on Windows before it has ever paired; browsentic mcp exits when its client goes away, on every platform; a CLI that exits before reading its input can no longer crash the daemon (#46, [#47])
• Windows stays experimental: a Claude Code run from the side panel has worked on a Windows 11 desktop, but the app, a cancelled run and the other agents have not been through one yet. The installer is not code-signed, so a downloaded copy meets SmartScreen; the one-line install does not (#46, [#47])

0.7.10 · Codex through its app-server, and follow-ups that reach the model

• Codex runs through its app-server, with the browser tools as its own. They are in the model's list from the first request instead of hidden behind a search, replies stream as they are written, and the context meter counts each request. If the app-server cannot start, the same turn falls back to codex exec; "transport": "exec" under agents.codex chooses it outright (#45)
• A Codex run is kept to the browser. Your own Codex MCP servers no longer start beside it (a -c override had merged into config.toml and started every one, with no approval gate), its shell and image viewer are off, and a shell command or file change stops the run as AGENT_UNSAFE (#44, [#45])
• Follow-ups carry what changed, on Claude Code and Codex. Both resend the prompt a session began with, so an A-Eye pick, an attached skill, a re-routed skill or new site notes never reached the model after the first turn. What changed now travels inside the follow-up's own message (#44)
• A Claude Code run whose browser tools failed to start stops instead of answering without the page. Codex now reads images in the file and captcha analysts; PDFs stay with Claude Code (#44)
• Antigravity follow-ups reach the browser. A resumed conversation re-read the folder it began in, so every turn after the first was refused with RUN_INACTIVE. A conversation now keeps one folder, rewritten each turn. Start a new Antigravity conversation after updating (#42)
• Antigravity is told where the page is. It ranked Browsentic's prompt beneath its own coding-agent identity and ran shell commands for questions about the page; it now reaches the page only through the browser tools (#42)
• Antigravity's timeline shows each action once, and a tool row stops sweeping when its turn ends, for every agent, saved conversations included (#42)

0.7.9 · Settings, on a page of their own

• A full-tab settings page with Appearance, Guardrails, Agent and Connection, in place of the side panel's Settings tab. Open it from the sliders button in the panel's header, the popup, the connection sheet, or the browser's own Options entry. No new permission (#43)
• One set of settings, wherever you change them. The theme and the guardrails live in ~/.browsentic/config.json, so every paired browser, the Mac app, the CLI and a hand edit of the file see each other's changes as they happen (#43)
• The Mac app's Settings tab sets every browser's theme and guardrails, and offers a restart when the running daemon is older than the app (#43)
• A run cannot loosen its own rules: a connection that has carried an agent run is refused a settings change (#43)

0.7.8 · Scheduled tasks, and a browser that starts the daemon

• Run an instruction or a recording on a schedule: once, on chosen days at chosen times, or every so many minutes within a daily window, in local time across daylight saving. Each run gets a background tab of its own; a recording replays without spending tokens, and hands over to the agent if a step fails (#37, closes [#32])
• A Schedules tab lists each task with its next run, its last result and a pause switch, with Run now, the last three transcripts and Pause all. Schedule from the clock beside the message box, "Repeat this…" under a sent message, or "Schedule" on a recording; browsentic tasks does the same from a terminal (#37)
• A run missed while the computer slept, the browser was closed or the daemon was down is logged, then run once when it is back or skipped, as the task says. An approval nobody is watching appears as a card on the page in front of you (#37)
• The browser starts the daemon when it is down, through a native messaging host that npx browsentic setup or update registers for Chrome, Edge, Brave, Vivaldi, Arc, Chromium and Firefox. browsentic stop still stays stopped until something starts it on purpose (#37)
• An approval that takes longer than a minute no longer fails the agent's call with DAEMON_UNREACHABLE, in scheduled runs and side-panel runs alike (#37)
• The panel no longer sits on Reconnecting after a sleep. Two dials at once made the daemon replace one socket with the other, over and over, while a working link sat underneath (#41)

0.7.7 · Hands-free

• Put the side panel away and talk to the page. A header button or /hands-free folds the panel into a mic on the page: your words appear as you say them, a ring runs before sending, and a press discards, stops a run or opens an approval. Hover for a menu; long-press to drag it anywhere (#40, closes [#39])
• Hold to talk: with it on, the mic listens only while left Control is held (#40)
• Offered only where speech works: Chrome and the Chromium browsers whose speech service answers. Never Firefox or Brave, which cannot transcribe (#40)
• A-Eye never outlines or picks what Browsentic draws on a page (the rail, a notice, the mic), and the agent's clicks pass through them (#40)

Documentation

• New guides for scheduled tasks, hands-free mode, the settings page and the Windows app, and a Windows is experimental section in the limits that says what one Windows desktop has shown so far
• The agents guide, configuration, guardrails, errors and troubleshooting cover the Codex app-server, the Antigravity changes and Windows. The internals set Claude Code and Codex side by side, and describe the Windows app

Install

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

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

The Browsentic-0.7.11.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.7.11-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.7.11 setup

That installs the extension, starts the daemon and prints a pairing code. Then load the folder it names at chrome://extensions with Developer mode on, and paste the code into the popup.

Firefox — 140 or newer:

:::sh
npx browsentic@0.7.11 setup --browser firefox

That prints the link to browsentic-0.7.11-firefox.xpi below, signed by Mozilla, and a pairing code. Open the link in Firefox, accept both prompts, and paste the code into the popup. Firefox updates the add-on by itself from then on. If the command says the file is not attached yet, Mozilla is still signing it.

Already running an older version? npx browsentic update refreshes the command and the extension in place and keeps your browser paired. Press ↻ on the Browsentic card afterwards; Firefox needs nothing pressed, and the Mac and Windows apps offer the update on their Overview tab.

From the zips, or from source

The `-chrome.zip` and `-firefox.zip` below are the same builds, for loading by hand. Release Firefox installs only the signed `.xpi`; the zip is for Developer Edition or Nightly. :::sh git clone --branch v0.7.11 https://github.com/imshaikot/browsentic.git cd browsentic && yarn setup && yarn daemon:link browsentic setup

Full changelog: https://github.com/imshaikot/browsentic/compare/v0.7.6...v0.7.11