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: cover the renamed check scripts and the daemon restart command
Shahriared6722a0729d
diff --git a/README.md b/README.mdindex 9ff675e..38519f8 100644--- a/README.md+++ b/README.md@@ -13,10 +13,11 @@ It runs on **an agent CLI you already have logged in** — [Claude Code](https:/## Features- **Voice or text.** Hands free dictation in the side panel, press to talk in the popup, plain typing anywhere.-- **Real page control.** 34 page capabilities covering reading, clicking, typing, form submission, navigation, screenshots, captcha handling, theming and accessibility, and background progress monitoring.+- **Real page control.** 35 page capabilities covering reading, clicking, typing, dragging, form submission, navigation, screenshots, captcha handling, theming and accessibility, and background progress monitoring.- **Site maps.** Point Browsentic at a site and it explores it, then writes reusable notes so later sessions already know their way around. See [Site maps](#site-maps-teach-it-a-site-once).- **Recordings.** Do a repetitive job once yourself and Browsentic keeps it as ordered steps, so "do it like last time" repeats it. See [Recordings](#recordings-show-it-once-repeat-it-later).- **Instant commands.** "Go back", "scroll to the top", "open github.com" run in the browser in milliseconds instead of becoming an agent run.+- **A conversation per tab.** Several tabs can work at once, each in its own conversation and each staying in its own tab. The side panel follows whichever tab is in front, a collapsible strip lists the ones running, and closing a tab ends its session and files the transcript in History.- **Bring your own agent.** The side panel runs on Claude Code, Codex or Antigravity — chosen from the status pill in the side panel or from the popup, either of which tells you which ones are installed and what a missing one needs.- **Works as an MCP server.** Claude Code or any other MCP client can drive your real, logged in browser through the same local daemon.- **Off by default.** A fresh install connects to nothing until you redeem a one time pairing code.@@ -224,7 +225,7 @@ to the agent, as does any local command that runs and fails.claude mcp add browsentic -- browsentic-mcp```-Claude Code now has 34 page tools plus `browsentic_status`, and three read only resources that+Claude Code now has 35 page tools plus `browsentic_status`, and three read only resources thatreturn page context without spending a tool call. Tool definitions are generated from the sameregistry the extension ships, so they cannot drift from what the browser can actually do.@@ -233,7 +234,7 @@ registry the extension ships, so they cannot drift from what the browser can act| Category | Capabilities || --- | --- || Read | Structured page snapshot with a layout diagram and stable selectors, rendered text or HTML, wait for an element to appear or vanish, screenshot the tab or one element |-| Act | Click, hover, focus, type into inputs and contenteditables, stream text in keystroke by keystroke at a human pace, choose a `<select>` option, select text, press keys with modifiers, submit a form, and — for pages that only accept a genuine gesture — click with a real browser-level mouse event |+| Act | Click, hover, focus, type into inputs and contenteditables, stream text in keystroke by keystroke at a human pace, choose a `<select>` option, select text, press keys with modifiers, submit a form, drag one thing onto another — reordering a list, moving a card between columns, pulling a slider — and, for pages that only accept a genuine gesture, click or drag with a real browser-level mouse event || Captchas | Identify the widget behind a "verify you are human" block, reading through the closed shadow roots and cross-origin frames vendors hide it in, and tick its checkbox with a real click. An image challenge is handed back to you to answer || Move | Open a URL, back, forward, reload, scroll to an element or position, open a URL in a new tab, list and switch between open tabs, close one || Files | List files stored in Browsentic and attach one to a file input on the page |@@ -280,9 +281,13 @@ browsentic-mcp sessions # which browsers are pairedbrowsentic-mcp revoke # unpair everything, or one originbrowsentic-mcp skills # every skill in scope, and where it came frombrowsentic-mcp logs # run starts, routed skills, every tool call+browsentic-mcp restart # swap the running daemon for a fresh onebrowsentic-mcp stop```+There is no start command: the first CLI or MCP client that needs the daemon spawns it, and it+lives until you stop it or it sits idle for 30 minutes with nothing attached.+## Privacy and security- **Nothing connects until you pair.** An unpaired extension never contacts the daemon.@@ -320,16 +325,16 @@ yarn dev # build, launch a throwaway Chrome profile, hot reloadyarn dev:firefoxyarn build # production buildyarn zip # store ready archive-yarn compile # type check-yarn intent:check # route a fixture table of utterances through the local grammar+yarn check # everything a pull request needs: both type checks, both fixture suitesyarn mcp:build # rebuild the daemon and MCP server+yarn mcp:restart # rebuild, then swap the running daemon for the fresh buildyarn mcp:manifest # print the tool manifest, no browser needed```Explain a single routing decision:```sh-yarn intent:check "take me to the checkout page"+yarn check:intent "take me to the checkout page"```Yarn 4 is the package manager and the release is pinned inside the repository, so whichever `yarn`@@ -346,8 +351,8 @@ module are load bearing at runtime rather than at compile time: touch `document`inside `execute()`, keep underscores out of action names, `.describe()` every input field, andvalidate with `ActionError` inside `execute()` rather than zod `.refine()`/`.transform()`.-Before opening a pull request, run `yarn compile`, `yarn compile:mcp`, `yarn intent:check`,-`yarn security:check` and `yarn mcp:manifest`.+Before opening a pull request, run `yarn check`. If you touched the action registry, also run+`yarn mcp:manifest` and keep [docs/tools.md](docs/tools.md) in step with what it prints.## Licensediff --git a/docs/installation.md b/docs/installation.mdindex 5281652..2575846 100644--- a/docs/installation.md+++ b/docs/installation.md@@ -378,10 +378,10 @@ Then reload the extension at `chrome://extensions` (↻ on the Browsentic card)daemon:```sh-browsentic-mcp stop+browsentic-mcp restart```-It restarts automatically on the next call. **Rebuild both halves together.** If only one side is+**Rebuild both halves together.** If only one side isrebuilt, `browsentic-mcp status` reports `manifest: DRIFTED` — the daemon falls back to the toolsthe browser actually has and tells your MCP client the list changed, but you should fix the driftrather than run on it.@@ -412,7 +412,7 @@ which live in extension storage.| "That pairing code is wrong or expired" | Codes are single-use and last 10 minutes | `browsentic-mcp pair` for a fresh one. A failed attempt does not burn the outstanding code. || "No Browsentic daemon is running" | Nothing on 8765–8767 | `browsentic-mcp status`; check the log with `browsentic-mcp logs` || Tools missing from an MCP session | The server was registered mid-session | Restart the client session — MCP servers load at start |-| `manifest: DRIFTED` | Extension and CLI built from different registries | `yarn build && yarn mcp:build`, then reload the extension |+| `manifest: DRIFTED` | Extension and CLI built from different registries | `yarn build && yarn mcp:restart`, then reload the extension || `AGENT_MISSING` | The chosen agent CLI is not on the daemon's `PATH` | `browsentic-mcp agent` to see all three; set `agents.<name>.bin` to an absolute path in `config.json` || `AGENT_NEEDS_PERMISSION` | Antigravity has no rule allowing Browsentic's MCP tools | Press the button in the popup, or run `browsentic-mcp agent setup antigravity` || "does not understand the flags Browsentic uses" | The agent CLI is too old | Update it |@@ -421,7 +421,7 @@ which live in extension storage.| `EXTENSION_OFFLINE` | Browser closed, or not paired | Open the browser; `browsentic-mcp sessions` to check pairing || `TAB_UNREACHABLE` on a normal site | The extension needs reloading | ↻ at `chrome://extensions`; ordinary sites otherwise self-heal || `RUN_IN_PROGRESS` | One instruction at a time | Cancel the running one in the side panel |-| An action ran but nothing appears in `logs` | It matched the local intent grammar and never reached the daemon | Expected — those carry a ⚡ on the timeline. `yarn intent:check "<what you said>"` explains the routing. |+| An action ran but nothing appears in `logs` | It matched the local intent grammar and never reached the daemon | Expected — those carry a ⚡ on the timeline. `yarn check:intent "<what you said>"` explains the routing. |Useful commands:@@ -434,6 +434,7 @@ browsentic-mcp skills # every skill in scope, and where it came frombrowsentic-mcp tools # the tool manifest, no browser neededbrowsentic-mcp logs # run starts, routed skills, every tool callbrowsentic-mcp token # the control token, for MCP clients+browsentic-mcp restart # swap the running daemon for a fresh onebrowsentic-mcp stop```@@ -449,15 +450,23 @@ yarn dev:firefoxyarn build # production buildyarn zip # store-ready archiveyarn compile # type check the extension-yarn compile:mcp # type check the daemon+yarn mcp:compile # type check the daemonyarn mcp:dev # rebuild the daemon on change+yarn mcp:restart # rebuild, then swap the running daemon for the fresh buildyarn mcp:manifest # print the tool manifest, no browser needed-yarn intent:check # route a fixture table of utterances through the local grammar-yarn security:check+yarn check:intent # route a fixture table of utterances through the local grammar+yarn check:security```-Before opening a pull request, run `yarn compile`, `yarn compile:mcp`, `yarn intent:check`,-`yarn security:check` and `yarn mcp:manifest`.+The daemon has no start command: the first CLI or MCP client that needs it spawns it, and it lives+until `browsentic-mcp stop` or 30 idle minutes with nothing attached. The flip side is that a+rebuild alone changes nothing while a daemon is running — it keeps the old code in memory. That is+what `yarn mcp:restart` is for: it rebuilds, stops the stale daemon and brings up the fresh build.+The extension cannot spawn the daemon; it only reconnects to one.++Before opening a pull request, run `yarn check` — it chains both type checks with both fixture+suites. If you touched the action registry, also run `yarn mcp:manifest` and keep+[tools.md](tools.md) in step with what it prints.See [architecture.md](architecture.md) for how the pieces fit together, and[features.md](features.md) for what they do.