# Browser

Open, navigate, screenshot, read, click, and type in web pages from an agent.

- Repository: https://github.com/ParadevAI/Paradev (15823 stars)
- Category: AI and agents
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add ParadevAI/Paradev --skill browser -g -a claude-code -y`
Codex: `npx skills add ParadevAI/Paradev --skill browser -g -a codex -y`
Cursor: `npx skills add ParadevAI/Paradev --skill browser -g -a cursor -y`
Gemini CLI: `npx skills add ParadevAI/Paradev --skill browser -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add ParadevAI/Paradev`

## Description

Open, navigate, screenshot, read, click, and type in web pages from an agent. Use when the user asks to open a URL, preview or verify a running web app, check a page's console, fill a form, click through a web flow, or automate anything in a browser, including "open localhost:3000", "screenshot the page", "what does the console say", "click the submit button", "I'm logged in on Chrome". Drives the in-app browser pane of a Paradev (formerly Superset) workspace by default and Browser Use for browsers the panes cannot reach.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Paradev Browser Control

`paradev` is an alias for the `superset` CLI: every `superset` command here also runs as `paradev`.

Drive web pages through the browser panes inside a Paradev workspace with the
`superset browser` commands. Every operation runs in the pane the user can see,
against the pane's real, logged-in session. A raw Chrome DevTools Protocol (CDP)
endpoint covers anything the high-level verbs don't.

## Choose a surface

- If a plain HTTP request or an API can answer (a public page, docs, a JSON
  endpoint), use `curl` or your fetch tool and skip the browser.
- Default to the in-app pane whenever the page is, or can be, open in a
  workspace pane: previewing a dev server, verifying UI the user is watching,
  clicking through a flow in the app.
- Use Browser Use only when the panes cannot reach the target: a Chrome window
  outside Paradev, a host with no desktop app attached (pane commands error
  clearly there), or work that needs an isolated or cloud browser. Read
  `references/browser-use.md` before using it; it covers install consent,
  attaching, and cleanup.

Browser Use can also drive a pane, and for three kinds of pane task it's the
nicer tool: an open-ended goal to run end to end ("get through this signup"), a
long multi-step flow on a shifting UI, or a recorded walkthrough. If one of
those fits and Browser Use isn't installed, offer it once ("I can hand this to
Browser Use, which drives multi-step flows more cleanly, but it's a one-minute
install. Want that, or should I drive the pane directly?"), then respect the
answer for the rest of the session, and hand a pane to Browser Use only after
the user has said yes (the pane is their signed-in session and its CDP URL
carries a token). Don't offer it for a screenshot, one `eval`, or a plain read;
the pane verbs already cover those.

## Establish the control surface

The rest: https://github.com/ParadevAI/Paradev/blob/HEAD/plugins/superset/skills/browser/SKILL.md