Release notes for every version

• Browsentic Home on every new tab: type a task, open a frequent site or pick up a recent conversation; Settings → Extension → New tab turns it off. (#75)
• Pairs by itself: the extension connects to Browsentic Bridge with no code, and browsentic pairing ask has each new browser wait for your Allow in the app or the terminal. (#73)
• Notifications on your computer: a finished monitor, scheduled task or reminder shows as a macOS or Windows notification through the Browsentic app while the browser is behind. (#74)
• Lighter agent turns: Claude Code, Codex, OpenCode and Mistral Vibe runs list the core page tools and reach the less common ones on demand, so every turn sends fewer tool schemas. (#71)
• Replies flow in word by word at a steady pace, however the agent sends them. (#72)
• The hands-free orb glows in your theme's accent instead of the same magenta in every theme. (#72)
• OpenCode 2 runs the side panel too, with a sign-in of Browsentic's own; OpenCode 1 works as before. (#76)
• Setup from the extension: with no Bridge on the computer, the welcome page and the connection card show the one-line setup command, with Copy. (#73)

• Every installed browser can start the Bridge: a Mac with Brave or Opera and no Chrome, a Mac whose Firefox never made a Mozilla folder, and Firefox on Windows for a user without admin rights. (#73)

Pairing by itself and notifications need this extension and this Bridge both; either one alone still works with a 0.8 peer as before.

• The phone tab: the side panel's Android switch, or /android (also /phone) in the composer, opens a tab beside the current one showing Chrome on the phone live in a phone frame, following whichever tab is in front on the phone. Click the picture to tap, scroll to scroll, type to type, with back, forward, reload, an address bar and the phone's tabs above it. The stream pauses while the tab is hidden or the phone's screen is off. Typed again, /android takes you back to the desktop. (6a110d4, 2ab90de, 81f5076)
• The agent works on the phone: a conversation in the phone tab drives the phone. Clicks and drags are real touches, typing and keys are real input, scrolling is a real scroll (so content that loads as you scroll does load), and screenshots come from the phone at the page's size. Tabs mean the phone's Chrome tabs. Agent working shows on the phone frame during a run, and the phone stays yours to use meanwhile. (5f2065d, d52a529, c17cea4)
• Only what works on the phone is offered: the Bridge withholds, and refuses, every tool that does not apply there (hover, captchas, downloads, uploading a file to a page, recordings, a site's own tools, monitors, diagnostics). On the phone tab the panel hides recordings, schedules, action cues and hands-free; switching back to a desktop tab brings them back. (bec117c)
• A phone-shaped prompt: a phone run is told up front where it is. It gets a phone skill that names only the tools it is offered, and the device in one line (model, Android, Chrome, viewport), so it spends no tool call finding out. The turn is about 30 KB smaller than a desktop one. A conversation that moves between the phone and a desktop tab is told in its next message. (204ddd0)
• A-Eye on the phone: the lens comes up on the phone tab's picture. Hovering outlines the element on the phone, a click picks it without pressing it (disabled buttons, links, fields and touch-handled elements included), a drag still scrolls, ↑ widens and Esc cancels. The pick carries the element's photograph from the phone, and the agent's own pick works the same way. (feb129c, ce287d7)
• Live tools on the phone: with Live tool on, page code you approve installs in the phone's page over DevTools and runs there. A kept tool saves for that site and runs with / on the phone tab. Running a tool on every visit stays desktop only. (4a4e13f)
• Guardrails hold on the phone: blocked sites are checked against the phone's own address and every frame on the focused path, before and after each tool, and a phone tab on a blocked site is never listed, matched, named or closed. Approvals work as they do on a desktop tab, and a run stays bound to the phone it started on. (5f2065d, 5048a9e)
• Readiness checks in every surface: browsentic android lists each check with its fix, browsentic android open [url] opens Chrome on the phone, and browsentic status gets an Android line that never starts adb. The Mac and Windows apps get an Android tab with the same checklist, and on Windows a link to the USB drivers many phones need. (87fcece, 9167cf6, 6172a27)
• The Bridge finds adb and relays DevTools: adb is found on PATH, in the Android SDK, and where Homebrew, winget, Scoop and Chocolatey put it. Phones are followed through adb's own server, and the Chrome DevTools Protocol is relayed between the extension and the phone, one session per phone, owned by the browser that opened it, with screencast frames dropped rather than queued when the browser falls behind. "android": { "enabled": false } in config.json turns it all off. (795546e, df28fbf, 1ec81be)
• Sessions end cleanly: unplugging the phone, closing Chrome on it, stopping the Bridge or closing the phone tab ends the session, says why, and offers Reconnect. A run in progress is told the phone is gone and stops. No adb port forward is left behind, and an open still in flight is cancelled. (2f37ba0, c17cea4)
• Version skew is safe: protocol 23 carries the Android frames and sends them only to a peer that speaks 23, so a 0.8.1 extension with this Bridge, or this extension with a 0.8.1 Bridge, connects and works on desktop tabs as before, without the Android switch. (cc134de)

What you need: a Chromium browser (Firefox has no Android switch), adb from Google's platform-tools, and an Android phone with Google Chrome, connected over USB or paired with adb over Wi-Fi (Android 11 or later). One phone at a time, and the phone's screen has to stay on while the agent works.

• The toolbar button opens the side panel, with no popup in between: Chrome and Edge through the side panel's own behaviour, Firefox by toggling its sidebar. A Chromium browser without a side panel keeps the popup as a launcher. (126d3b7)
• An update pill: once the browser has downloaded a newer extension, Browsentic vX is ready offers Update above the prompt, which restarts the extension onto it instead of waiting for an idle moment a live Bridge never allows. It waits while any conversation has a run going or a recording is on. A Bridge newer than the extension asks the store at once, and an unpacked copy offers the folder the Bridge rewrote. (1a537c3, 0194ace)
• The composer: the attach-page button is gone, since the agent reads the page's title, address and selection itself, and Attach a file takes the paperclip. The / menu scrolls to keep the highlighted command or skill in view and names it for screen readers. (8865032, fcb2fef)
• Pairing: the pairing card links to the install guide's pairing step, for anyone who added the extension from its store page and never saw what a pairing code is. (f75b6a8)

• Edge installs from the Chrome Web Store again, which approves updates far sooner than Edge Add-ons. Setup, browsentic browsers and the apps open it in Edge and say to allow extensions from other stores first. Copies installed from Edge Add-ons still pair and update. (623ccfb)
• Five tabs in the apps: Agents, Skills, Activity and Logs become pages of Settings, picked from a sidebar beside General, which makes room for the Android tab. The Mac menu bar shows the Browsentic mark, its centre dot filled while the Bridge runs. (1dc8a0e)

• The Bridge's wake-up registers with each installed Windows browser through the key that browser reads, the Beta, Dev and Canary channels of Chrome, Edge and Brave included, with no console window, and its launcher survives a home folder like C:\Users\José. (6880e5b, 5ff2118)
• browsentic-mcp with no arguments serves MCP on Windows too, where npm's shim loses the name it was called by. (ee4377e)
• A self-update hands the rerun every argument whole, so setup --dir with a space in the path is not split. (1f0e8d0)
• Uninstall carries on past a file Windows will not delete, so the pairing keys still go, and removes only the link to a linked folder, never what it points at. (5e9f980, 5ff2118)
• A folder in config.json may start with ~\. (709c986)
• The unpacked steps say how to paste the path into the folder picker on Windows and Linux, not only macOS. (99a1874)
• The adb server the Bridge starts no longer holds open the folder the Bridge started in, and on the phone tab AltGr and Option type their characters. (1ec81be)

• extension: a star request after a clean turn: a Star us on GitHub pill floats above the composer when an agent finishes a turn in the conversation on screen; Star opens the repository beside the current tab and retires it for good, and × or the next instruction takes it down; it asks at most once in a conversation and three times in all: in the first conversation, the next one, and three conversations after that (24c0b3c, 3076a41, c8f595b)
• extension: action cues: a glowing ring on every element an agent acts on, captioned with the action and the element’s name, and the page’s edge for an action with no element; off until switched on from the composer, the mic’s menu or Settings, drawn in a closed layer that never touches the page, and cleared before any screenshot (4be846f)
• setup: Edge gets the extension from its own Edge Add-ons listing, now that Microsoft has published it: setup, browsentic browsers and the apps open it with a plain Get, and the README, the install guide, the npm page, the DMG readme and the release notes link it instead of sending Edge to the Chrome Web Store (c95d5ad)

• extension: action cues stay out of the page's way: the caption's font rule is valid again, a page's ::backdrop rule can no longer dim the screen, a trusted click leaves the cue host's attributes alone, a field is named by its label without its own text, a lit frame is remembered past a hidden tab's throttled fade so a later screenshot still quenches it, and a hidden tab answers without waiting for frames that never come (9ed6f5f)

• 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)

• 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)

• 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)