Skip to content

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.

feat(android): docs: live tools and A-Eye on the phone

Shahriarffd453bb90a0
diff --git a/docs/guide/features/android.md b/docs/guide/features/android.md
index 135b83b..1d08bc5 100644
--- a/docs/guide/features/android.md
+++ b/docs/guide/features/android.md
@@ -82,16 +82,25 @@ phone's tabs, and timers. The differences:
[Blocked sites](blocked-sites.md) are checked against the phone's own address, and
[approvals](../approvals.md) work as they do on a desktop tab.
+**[A-Eye](a-eye.md)** works on the phone tab too. Press its button in the side panel, and when the
+lens shows on the phone, click the element on the phone tab's picture: that tap picks it rather
+than pressing it, and the pick carries a photograph of the element from the phone. When the agent
+asks you to point at something, it works the same way.
+
+**Live tools** work there as well. With the Live tool switch on, the agent can write code for the
+phone's page; you approve it before it runs, as on a desktop tab. You can keep the result as a
+saved tool and run it with `/` on the phone tab. A saved tool can't run on every visit on the
+phone, because nothing of Browsentic is installed there.
+
## What is off on the phone
While the phone tab is in front, the side panel hides what only works in a desktop tab:
-[recordings](recordings.md), [scheduling](scheduling.md), live tools and saved tools,
-[A-Eye](a-eye.md), [action cues](action-cues.md) and [hands-free](hands-free.md). Voice in the
-panel, attaching a file and attaching the page's context still work. They all come back when you
-switch to a desktop tab.
+[recordings](recordings.md), [scheduling](scheduling.md), [action cues](action-cues.md) and
+[hands-free](hands-free.md). Voice in the panel, attaching a file and attaching the page's context
+still work. They all come back when you switch to a desktop tab.
The agent is offered only the tools that work on the phone. Hovering, captchas, downloads,
-uploading a file to a page, page code, a site's own tools, monitors and diagnostics stay on the
+uploading a file to a page, a site's own tools, monitors and diagnostics stay on the
desktop. If you ask for one of those, the agent says it is not available on the phone.
## Privacy and safety
diff --git a/docs/guide/limits.md b/docs/guide/limits.md
index e560e8f..e12f9ea 100644
--- a/docs/guide/limits.md
+++ b/docs/guide/limits.md
@@ -196,7 +196,10 @@ command or an MCP client instead.
the agent's actions can stall or fail. Keep the phone unlocked while it works.
- **USB, or Wi-Fi already paired with adb.** Browsentic does not pair a phone over Wi-Fi for you.
- **Desktop-only tools stay on the desktop**: hover, captchas, downloads, uploading a file to a
- page, page code, a site's own tools, monitors, diagnostics, recordings, scheduling and A-Eye.
+ page, a site's own tools, monitors, diagnostics, recordings and scheduling.
+- **Saved tools don't run on every visit on the phone.** They run with `/` on the phone tab; every
+ visit needs Browsentic in the page, and nothing of it is installed on the phone.
+- **Page code installs in the top document.** In a frame, the agent steps back out first.
- **Native pickers are out of reach.** A `<select>` opens the phone's own picker, which is not part
of the page; the agent sets its value instead. The same goes for permission prompts and anything
else Android draws over Chrome.
diff --git a/docs/internals/agent-runs.md b/docs/internals/agent-runs.md
index 058f0a5..379e293 100644
--- a/docs/internals/agent-runs.md
+++ b/docs/internals/agent-runs.md
@@ -491,23 +491,24 @@ Chrome versions, and the viewport, read when the message is sent. The run change
- **Its base skill is always `phone`** (`PHONE_SKILL` in `skills.ts`), whatever the words would
have routed to, even when a `@name` names another general skill. `browser-control.md` teaches
- desktop tools a phone run is not offered (hover, captchas, downloads, a site's own tools, page
- code), and naming a withheld tool invites the agent to try it. `phone.md` names only
- `PHONE_TOOLS`, and a test holds it to that. Site notes for the phone page's host still ride
- along; the page-scripting overlay never does, even with `liveTools` set. Like `page-scripting`,
+ desktop tools a phone run is not offered (hover, captchas, downloads, a site's own tools), and
+ naming a withheld tool invites the agent to try it. `phone.md` names only `PHONE_TOOLS`, and a
+ test holds it to that. Site notes for the phone page's host still ride along, and the
+ page-scripting overlay does with Live tool on, as on desktop. Like `page-scripting`,
`phone` is a `general` skill kept out of desktop routing by name.
- **Its prompt opens on the phone** (`PHONE_OPENING` in `prompt.ts`): every tool call lands on the
tab in front on the phone, not on "whichever tab is frontmost". The numbered rules are the same.
- **An `# Android phone` section** carries `phoneBlock(context.phone)`, such as
`Pixel 8 · Android 16 · Chrome 150 · viewport 411×915 CSS px at 2.625x`, so the agent needs no
tool call to learn the device. It holds no address, so it does not change with every message.
-- **Its tool list is smaller.** `offerFor` withholds every tool off `PHONE_TOOLS`, and
- `invokeForRun` refuses a call to one with `NOT_ON_PHONE`. The tool list the browser describes
+- **Its tool list is smaller.** `offerFor` withholds every tool off `PHONE_TOOLS`, and the
+ page-code tools unless Live tool is on, and `invokeForRun` refuses a call to one with
+ `NOT_ON_PHONE`. The tool list the browser describes
is never varied, because it feeds the manifest hash.
-Together these make a phone run's fixed overhead about 40 % smaller than a desktop run's: measured
-as sent on 9 Oct 2026, the repository's part of the system prompt was 7.9 KB against 19.6 KB, and
-the tool list 31 tools in 39.6 KB of JSON against 52 in 60.7 KB.
+Together these make a phone run's fixed overhead close to 40 % smaller than a desktop run's:
+measured as sent on 10 Oct 2026 with Live tool off, the repository's part of the system prompt was
+9.0 KB against 20.7 KB, and the tool list 33 tools in 41.0 KB of JSON against 52 in 60.7 KB.
A conversation can move between the phone and a desktop tab when it is restored onto the other. A
CLI that keeps its first prompt then hears the change in its next message: the `phone` and `skill`
diff --git a/docs/internals/android.md b/docs/internals/android.md
index 3eddf3c..64973e8 100644
--- a/docs/internals/android.md
+++ b/docs/internals/android.md
@@ -172,10 +172,34 @@ someone makes it work there and adds it, with a test. `HOST_SIDE` lists the tool
The tool list a browser describes, and so its manifest hash, never changes for the phone. Instead
`AgentSession.offerFor` withholds every tool `phoneOffers` rejects for a run whose context carries
-`phone`, and `invokeForRun` refuses a call to one. On the phone tab the side panel hides recordings,
-schedules, live tools and saved tools, A-Eye, action cues and hands-free, by the phone tab's id
-(`useMirroredPhone` in `phone-client.ts`), because without the `tabs` permission an extension
-page's URL is hidden from the panel.
+`phone`, plus the page-code tools unless Live tool is on (the desktop rule), and lists
+`browsentic_focusShot` for a pick's photograph. `invokeForRun` refuses a call to a tool off the
+list. On the phone tab the side panel hides recordings, schedules, action cues and hands-free, and
+every saved tool's "every visit" switch, by the phone tab's id (`useMirroredPhone` in
+`phone-client.ts`), because without the `tabs` permission an extension page's URL is hidden from
+the panel.
+
+## Live tools on the phone
+
+`code-toolkit.ts` keeps each approved toolkit for a **place** (`ToolkitPlace`): a desktop tab
+(`tabPlace`), or the phone's front tab (`phoneToolkitPlace` in `phone-backend.ts`, keyed
+`phone:<targetId>`). On the phone the installer is evaluated in the top document's main world with a
+plain `Runtime.evaluate` over the relay, which no page CSP can refuse. Calls run `page.runCode`'s own
+page side in the bundle's isolated world, which reaches the toolkit by DOM events exactly as the
+desktop content script does. `toolkitPlaceFor` in `phone-invoke.ts` picks the place for the panel's
+`keepTool` and `/` run. Every-visit tools need `chrome.userScripts` in the page, so they stay desktop
+only.
+
+## A-Eye on the phone
+
+`page.pickElement` runs its own lens in the bundle's world on the phone. A click on the phone tab's
+picture arrives as a tap, and the lens takes the click that follows it and swallows it, so the page
+never sees it. The wait is capped at 170 s, under the relay's 180 s per command, so the page's own
+timeout answers first. `pickOn` then photographs the element: `pickClip` pads its box, keeps it on
+screen, moves it into document coordinates (plus any frame's offset), and asks `Page.captureScreenshot`
+for it at device resolution, up to 1,200 px on the long side. The panel's A-Eye button reaches the
+phone through the background (`pickFocus` in `aeye.ts` sends the `invoke` bridge op), because the
+panel cannot reach the socket.
## The prompt