command-center/omp-docs/pi/packages/pi-browser-use.md at main

Files

T

Frank 99b9a6a17c docs(pi): unify split package trees; move live OMP pages to core

Two directories documented one concept (pi npm packages): top-level
packages/ (browser-use, permission-system) and pi/packages/ (peon,
web-access, subagents). Merged into pi/packages/ — one row per package
in a single index, detail pages kept as archive records. The root
index's 'OMP packages and skills' section was doubly wrong (packages/
was pi, not OMP); it becomes a Skills tooling section pointing at the
consolidated /skills/ tree.

Moved the two LIVE omp pages out of the retired-harness banner:
pi/statusline.md -> core/statusline.md, pi/subagent-limits.md ->
core/subagent-limits.md (both document omp behavior against
agent/config.yml + the installed bundle; pi/index.md itself admitted
the mis-shelf). Retargeted every inbound link (core/index, system/
dankserver, log x2, pi/index, settings x2, moved files' own xrefs).

Refs #29

2026-10-19 03:32:07 -07:00

2.9 KiB

Raw Permalink Blame History

type, title, description, resource, tags, timestamp

type

title

description

resource

Features

Dynamic tool discovery — auto-proxies all upstream chrome-devtools-mcp tools with browser_ prefix
Tool description augmentation — adds usage hints for key tools
Result post-processing — strips embedded snapshots, detects overlay/stale element issues
Optional visual analysis — browser_analyze_screenshot via configurable vision model
Standalone mode — runnable as independent MCP server via CLI

Requirements

Node.js >= 20, Chrome (stable or newer), @earendil-works/pi-coding-agent >= 0.74.0.

Installation

pi install npm:@amaster.ai/pi-browser-use

Usage

As pi-coding-agent Extension (Recommended)

Auto-discovers and loads on session_start. Configure in .pi/settings.json:

{
  "pi-browser-use": {
    "headless": true,
    "channel": "stable",
    "viewport": "1280x720",
    "experimentalVision": true
  }
}

As Standalone MCP Server

npx @amaster.ai/pi-browser-use --headless --viewport=1280x720

Configuration

Session Mode

Mode	Description
`persistent` (default)	Reuses shared profile at `~/.pi/browser-profile`
`isolated`	Fresh ephemeral profile each session
`existing`	Connects to running browser instance

Browser Options

Option	Type	Default	Description
`headless`	`boolean`	`false`	Run headless
`channel`	`string`	—	Chrome channel: `canary`, `dev`, `beta`, `stable`
`viewport`	`string`	—	Viewport size, for example `1280x720`
`userDataDir`	`string`	—	Custom user data directory

Vision Model

{
  "pi-browser-use": {
    "visionModel": {
      "provider": "openai",
      "model": "gpt-4o"
    }
  }
}

Resolves API key and base URL from the model registry automatically.

Key Tools

Tool	Hint
`browser_click`	Use element uid from snapshot; UIDs invalidated after action
`browser_fill`	Does not work on canvas/custom widgets
`browser_press_key`	Accepts single key name only
`browser_take_snapshot`	Call first to get uids, and after every state-changing action

Cross-References

See Skills for the skill toolchain that replaced pi-package distribution.
See OKF Specification for the knowledge bundle format.

2.9 KiB Raw Permalink Blame History