An agentic browser harness: an AI side panel & orb in your own logged-in Chrome, Edge, Arc, Brave or even Firefox run by the agent/subscription you already use (Claude Code, Codex, Antigravity). Free, open source, no API key. Also an MCP server.
TypeScript agentic-browseragentic-browsingagy-cliaiai-agentai-browser-extensionai-toolsbrave-extensionbrowser-agentbrowser-automationbrowser-extensionbrowser-usebrowserskillchrome-extensionclaude-codecodexfirefox-addonmcp-servernanobrowserweb-automation
docs: why the native host starts the Bridge through launchd on macOS, and what to do about a .bun dylib that macOS will not open
Shahriar6ea54c160c95
diff --git a/docs/guide/troubleshooting.md b/docs/guide/troubleshooting.mdindex 9bb0517..c728875 100644--- a/docs/guide/troubleshooting.md+++ b/docs/guide/troubleshooting.md@@ -36,6 +36,7 @@ Those three answer most questions. The Bridge's log is at `~/.browsentic/daemon.| The panel says **Browsentic Bridge needs an update** | The Bridge on this computer is older than automatic pairing, or older than 0.8 and does not let store copies in | `npx browsentic@latest update`, or **Update now** in the app || The panel says **Browsentic Bridge was updated but the old one is still running** | Pairing is set to ask and the Bridge still running is the one from before the update | `browsentic restart`, or **Restart** in the app || Firefox on Windows wakes the Bridge, then it is gone again | Firefox ends everything a native host starts when the host exits | Setup registers a scheduled task (Task Scheduler, `Browsentic Bridge for <your user name>`) that starts the Bridge outside Firefox; run `browsentic setup` once if it was installed before that. Starting the Bridge from the app or `browsentic start` also works |+| macOS says **".bun-….dylib" Not Opened** because Apple could not verify it | A Bridge the browser started passed the browser's quarantine on to OpenCode, which unpacks a library into the temporary folder and loads it on every start. Bridges now start through launchd, outside the browser | Update the Bridge, then `browsentic restart` or **Restart** in the app. It deletes the quarantined copy as it starts, and OpenCode unpacks a fresh one || The side panel's **Connection** sheet shows `Expected {op:…}` | Stale service worker after a rebuild | At `chrome://extensions`, press ↻ on Browsentic || "That pairing code is wrong or expired" | Codes are single-use and last 10 minutes | Run `browsentic pair` for a new code. A failed attempt does not use up the outstanding code || "No Browsentic daemon is running" | Browsentic Bridge is not installed, or not running on 8765–8767 | [Install it](install.md#1-install-browsentic), open the app, or run `browsentic start`. Then check `browsentic status` and `browsentic logs` |diff --git a/docs/internals/extension.md b/docs/internals/extension.mdindex 87e626f..d1369db 100644--- a/docs/internals/extension.md+++ b/docs/internals/extension.md@@ -574,7 +574,10 @@ only; **Always on ‹site›** stays in the panel.`nativeMessaging` is what lets a browser start a daemon that is down. When no port answers,`giveUp` calls `wakeDaemon`, which asks the browser to run the `com.browsentic.daemon` host that-`browsentic setup` registered. That host runs `ensureDaemon` and exits. `browsentic stop` leaves+`browsentic setup` registered. That host runs `ensureDaemon` and exits. On macOS it starts the daemon+as a launchd job, not as its own child: a browser runs its native hosts quarantined, and a daemon+the host spawned would pass that on to every file it and its agents write, so Gatekeeper would+refuse any code they unpack (`src/daemon/quarantine.ts`). `browsentic stop` leaves`~/.browsentic/stopped` behind, and while it is there the host starts nothing; the next daemon tostart, by any other path, removes it.