Skip to content
Skills Library
AI & agents · Automation

agent-browser

/agent-browser

Use when the task needs a real web browser inside the sandbox - open a page, click, fill forms, take screenshots, extract or scrape data, test a web app, or use a site that needs a login. Drives the preinstalled agent-browser CLI; the browser window shows on the user's Desktop tab. This is NOT the local_browser tool, which controls the user's own Chrome on their computer.

Repository
weknora ↗
Licence
MIT
Last repository change
09.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the task needs a real web browser inside the sandbox - open a page, click, fill forms, take screenshots, extract or scrape data, test a web app, or use a site that needs a login. Drives the preinstalled agent-browser CLI; the browser window shows on the user's Desktop tab. This is NOT the local_browser tool, which controls the user's own Chrome on their computer.

Original author description

Use when the task needs a real web browser inside the sandbox - open a page, click, fill forms, take screenshots, extract or scrape data, test a web app, or use a site that needs a login. Drives the preinstalled agent-browser CLI; the browser window shows on the user's Desktop tab. This is NOT the local_browser tool, which controls the user's own Chrome on their computer.

How it works

  1. Start here
  2. Basic loop
  3. Screens
  4. Logins and codes
  5. Rules
Original SKILL.md headings · 80 lines, 541 words
SKILL.md preview
---
name: agent-browser
description: Use when the task needs a real web browser inside the sandbox - open a page, click, fill forms, take screenshots, extract or scrape data, test a web app, or use a site that needs a login. Drives the preinstalled agent-browser CLI; the browser window shows on the user's Desktop tab. This is NOT the local_browser tool, which controls the user's own Chrome on their computer.
---

# agent-browser (browser inside the sandbox)

The CLI is already installed. Do not install it again, do not run
`agent-browser install`, and never install a browser yourself: the sandbox
pins its own Google Chrome. Run it with shell_exec and without skill_name.
Every call is one command; the browser stays open between calls.

## Start here

This file is only the map. Load the real usage guide from the CLI itself, so
the instructions always match the installed version:

```sh
agent-browser skills get core        # workflows, common patterns, troubleshooting
agent-browser skills get core --full # adds the full command reference
agent-browser skills list            # specialized guides bundled with the CLI
```

For quick tasks the loop below is enough; read `core` before anything harder
(waits, iframes, multiple tabs, downloads, auth flows).

## Basic loop

```sh
agent-browser open https://example.com   # the window opens on the Desktop tab
agent-browser snapshot -i          # interactive elements as @e1, @e2, ...
agent-browser click @e2
agent-browser fill @e3 "text to type"
agent-browser screenshot /workspace/output/page.png
agent-browser close                # closes the browser; the screen stays
```

Run `snapshot -i` again after every page change: refs from an older snapshot
go stale. `agent-browser --help` lists every other command.

## Screens

The browser always opens as a visible window on the user's Desktop tab, so
the user can watch it and take over. Do not ask the user whether to show it,
and do not pass any flag to hide or show it. The user may click in the same
window while you work: run `snapshot -i` again before acting if the page may
have changed. Never ask for a password or code in the chat.

## Logins and codes

When a page asks for a username, password or one-time code and the
`request_secure_form` tool is available:

1. Call `request_secure_form` with the page's host as `site`.
2. Run `agent-browser snapshot -i` again, then call `browser_fill_secret` with
   the handle and the refs of the inputs.
3. Click the sign-in button yourself; the tool never submits.

Judge success by the statuses `browser_fill_secret` returns. Until you leave
that page, do not take screenshots, do not click "show password", and do not
read input values with `get value` or `eval`.

Without `request_secure_form`, or for a captcha, ask the user to type it into
the window on their Desktop tab.

## Rules

- Do not pass `--session`, `--profile`, `--cdp`, `--auto-connect`, `--state`
  or `--executable-path`. The sandbox supplies the profile, the session and
  the browser; those flags are discarded.
- Do not set DISPLAY, and do not target display :0. That screen belongs to
  other sessions.
- Close the browser only with `agent-browser close`. Never `pkill`/`kill`
  chrome or agent-browser processes: other sessions' browsers run on this
  machine too, and `agent-browser close` only ever touches this session's
  own browser.
- Cookie state is saved in a machine-level seed and restored before startup
  navigation. Live browsers mirror missing cookies and localStorage keys;
  existing keys are not overwritten. A receiving page may reload once idle.
  localStorage is shared from open pages, not persisted in the cookie seed.
  Cookie and password database files are shared; history, cache and IndexedDB
  stay in each profile. Signing out may affect shared login state. Windows
  remain on this session's screen. Never print cookie, password or token files.

Versions

RepositoryScoreLicence
This page · tencent/weknora100MIT
vanducng/skills100MIT
mvschwarz/openrig100Apache-2.0
mgiovani/cc-arsenal100MIT
desplega-ai/agent-swarm100MIT
nexu-io/open-design100Apache-2.0
seaworld008/commonly-used-high-value-skills100MIT
slopus/happy100MIT
j62268781-alt/dsh-toolkit100MIT

Database snapshot: 13.11.2026 · package version d7be2b9e1cd3 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100open-browser-agent
    Use when an AI agent needs to automate, browse, inspect, scrape, click, fill forms, or interact with web pages and web applications using the open-browser-agent MCP server or CLI
  • 92ai-browser
    Drive Chrome AI, the user's dedicated signed-in Chrome window, with the dev-browser CLI to open sites, read pages, click, fill forms, take screenshots and check a live app. Use when the user asks to browse, open a site, click, fill a form, take a screenshot, scrape a page, test…
  • 100browser
    Use for a web page on your computer, to open it, read it, fill forms, click, and take screenshots, with the agent-browser command, on the desktop's Chromium that your owner sees.
  • 100chrome-use
    Operate web pages in the user's own Chrome on their connected computer through the chrome-use command-line tool — open pages, read them as structured text, click, fill forms, upload files, take screenshots, and test web apps, using the sites the user is already signed in to. Use…
  • 100browser-use
    Control a real browser to navigate pages, click, type, fill forms, inspect rendered UI, take screenshots, or record video. Load only when the user asks to open or automate a browser, interact with or test rendered page UI, scrape a site that needs browser execution, or capture a…
  • 96gsd-browser
    Native Rust browser automation CLI for AI agents. Use when the user needs to interact with websites, navigate pages, fill forms, click buttons, take screenshots, extract structured data, run assertions, test web apps, mock network requests, or automate any browser task. Triggers…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.