Browser
Screenshots, styled PDFs, pages as Markdown, recordings and scripted flows on a browser the plugin installs for you, plus web search with an optional key.
The Browser pack gives your agent a browser of its own. Ask in plain words:
you > screenshot https://acme.com and call it acme-landing
you > render ~/Documents/business-plan.md to PDF
you > convert https://example.com to markdown, make sure the JS-rendered sections come through
you > record a 15-second tour of acme.com: scroll halfway, wait 2s, scroll to the bottomWhat it gives you
| Tool | Output | Use it for |
|---|---|---|
browser_screenshot | PNG | Any URL or local HTML / Markdown file; fullPage for the whole scroll |
browser_pdf | PDF (A4) | Markdown (Mermaid rendered) or HTML to print-styled PDF |
browser_markdown | Markdown | Any URL, including client-rendered SPAs, to clean LLM-friendly Markdown via Readability |
browser_record | WebM | Drive a page through navigate / scroll / wait steps and capture the run |
browser_flows | varies | Run a named, repeatable flow in a visible browser: scrape, fill a form, click through a task |
web_search | Results with citations | A direct call to the Perplexity Search API |
The five browser_* tools take the same input: a URL, a file:// URL, or a path. screenshot and pdf render local Markdown through a styled CSS so Mermaid comes through; markdown does the reverse. An explainer or pull-request page the engineer skill wrote is captured with its diagrams drawn, not their source.
Outputs land in <HOME>/reports/captures/<timestamp>-<name>.<ext>.
What it needs
- Nothing for the browser tools. They run on a Chromium of the plugin's own, about 300 MB with its headless shell. Setup downloads it with the plugin's packages, so there is nothing to install by hand.
- On Linux or WSL2, system libraries once. A fresh distro lacks the libraries Chromium links against. The first failed launch prints the fix: a
sudo … playwright install-deps chromiumline with your plugin path filled in. - For
web_search, a Perplexity API key. Optional and pay-as-you-go; costs are on Accounts and costs. Without it, briefings use your host's built-in web search. The key adds recency, domain and country filters and dated results.
Switch it on
Run configure-skills and pick Browser. Setup ticks it by default. The walk has two parts, and you can take either one alone:
- The browser tools. It grants the five
browser_*tools. Without the grant they still work, and the first call asks. - Web search. It grants
web_search. Then, in Perplexity → Settings → API, load a small credit block and generate a key. The API bills separately from a Pro chat subscription. Add the key in your editor, never in chat:
# <HOME>/.state/secrets/.env
PERPLEXITY_API_KEY=pplx-...Relaunch your host from the home so the key loads.
Flows
browser-flows drives a visible browser through pluggable flows; hacker-news ships as the reference. Write your own for any repeatable multi-step task on a site you use.
Your flows live in your home, one folder each under scripts/browser/<flow>/, with an index.ts to run and an optional index.md of guidance. A flow that needs a password or a card reads it from a .env in its own folder: the tool hands that file to that flow alone, it's gitignored, and the agent's own reads are denied. A flow with a built-in's name runs in its place. A flow's target can carry Chromium flags of its own (args), added after the shared ones, so a flow that needs a fake camera for a document-capture screen gets one without every flow granting media permissions.
A flow has a 15-minute cap: the 5-minute wait for you to log in, plus the run. A flow you cancel, or one that hangs past the cap, stops with its browser, and the result says it was cancelled or timed out.
If the browser won't start
Most failures are an unfinished download or uninstalled packages, and each error message carries its fix; find the message below.
Where it's used
Briefings, the browser-flows skill and the Reach and see group lean on this pack.