Core Guide for agent-browser
vercel-labs/agent-browser
Core usage guide for the agent-browser CLI: the snapshot-and-ref workflow for navigating, clicking, filling forms, extracting data and running parallel sessions.
Automates a real browser through short TypeScript scripts that keep page state between runs, for navigating, filling forms, taking screenshots and extracting data.
$ npx skills add MemTensor/MemOS --skill dev-browser -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MemTensor/MemOS dev-browser --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/MemTensor/MemOS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/openwork-memos-integration/apps/desktop/skills/dev-browser .claude/skills/dev-browser && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "dev-browser" agent skill from https://github.com/MemTensor/MemOS/tree/main/apps/openwork-memos-integration/apps/desktop/skills/dev-browser into .claude/skills/dev-browser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-browser", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/MemTensor/MemOS/tree/main/apps/openwork-memos-integration/apps/desktop/skills/dev-browserType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add MemTensor/MemOS --skill dev-browser -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MemTensor/MemOS dev-browser --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MemTensor/MemOS.git skills-src && mkdir -p .agents/skills && cp -r skills-src/apps/openwork-memos-integration/apps/desktop/skills/dev-browser .agents/skills/dev-browser && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dev-browser" agent skill from https://github.com/MemTensor/MemOS/tree/main/apps/openwork-memos-integration/apps/desktop/skills/dev-browser into .agents/skills/dev-browser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-browser", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MemTensor/MemOS --skill dev-browser -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MemTensor/MemOS dev-browser --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MemTensor/MemOS.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/apps/openwork-memos-integration/apps/desktop/skills/dev-browser .cursor/skills/dev-browser && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dev-browser" agent skill from https://github.com/MemTensor/MemOS/tree/main/apps/openwork-memos-integration/apps/desktop/skills/dev-browser into .cursor/skills/dev-browser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-browser", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/MemTensor/MemOS.git --path apps/openwork-memos-integration/apps/desktop/skills/dev-browser--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add MemTensor/MemOS --skill dev-browser -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MemTensor/MemOS dev-browser --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MemTensor/MemOS.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/apps/openwork-memos-integration/apps/desktop/skills/dev-browser .gemini/skills/dev-browser && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dev-browser" agent skill from https://github.com/MemTensor/MemOS/tree/main/apps/openwork-memos-integration/apps/desktop/skills/dev-browser into .gemini/skills/dev-browser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-browser", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install MemTensor/MemOS dev-browserInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add MemTensor/MemOS --skill dev-browser -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MemTensor/MemOS.git skills-src && mkdir -p .github/skills && cp -r skills-src/apps/openwork-memos-integration/apps/desktop/skills/dev-browser .github/skills/dev-browser && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dev-browser" agent skill from https://github.com/MemTensor/MemOS/tree/main/apps/openwork-memos-integration/apps/desktop/skills/dev-browser into .github/skills/dev-browser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-browser", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MemTensor/MemOS --skill dev-browser -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MemTensor/MemOS dev-browser --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MemTensor/MemOS.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/apps/openwork-memos-integration/apps/desktop/skills/dev-browser .opencode/skills/dev-browser && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dev-browser" agent skill from https://github.com/MemTensor/MemOS/tree/main/apps/openwork-memos-integration/apps/desktop/skills/dev-browser into .opencode/skills/dev-browser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dev-browser", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
dev-browserAutomates a real browser through short TypeScript scripts that keep page state between runs, for navigating, filling forms, taking screenshots and extracting data.
The skill keeps named pages alive across script executions, so the agent writes small scripts that each do one thing, such as navigate, click, fill or check, and logs state at the end to decide the next step. It picks an approach by situation: read the source of local sites to write selectors directly, use getAISnapshot() and selectSnapshotRef() to find and operate elements on unfamiliar pages, and take screenshots for visual feedback.
There are two modes. Standalone mode, the default, launches a new Chromium browser through server.sh and can run headless, and the agent waits for a Ready message before running scripts. Extension mode connects to your existing Chrome through a relay server, so automation runs in a session where you are already logged in, provided the extension is installed and active. Scripts run with npx tsx from the skill folder, and a reference note covers scraping.
2 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit a7367d0. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 2 files in scripts/ (TypeScript and Shell, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
npmnpxFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Dev Browser Automation loads about 1.7k tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 94 tokens; SKILL.md has 516 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from MemTensor/MemOS at commit a7367d0, republished under its Apache-2.0 licence (© MemTensor). 516 words, ~1,722 tokens.
.claude/skills/dev-browser/SKILL.md (or your agent's skills folder). This skill also uses 16 other files; get the full folder from GitHub.Browser automation that maintains page state across script executions. Write small, focused scripts to accomplish tasks incrementally. Once you've proven out part of a workflow and there is repeated work to be done, you can write a script to do the repeated work in a single execution.
getAISnapshot() to discover elements and selectSnapshotRef() to interact with themTwo modes available. Ask the user if unclear which to use.
Launches a new Chromium browser for fresh automation sessions.
./skills/dev-browser/server.sh &Add --headless flag if user requests it. Wait for the Ready message before running scripts.
Connects to user's existing Chrome browser. Use this when:
Important: The core flow is still the same. You create named pages inside of their browser.
Start the relay server:
cd skills/dev-browser && npm i && npm run start-extension &Wait for Waiting for extension to connect... followed by Extension connected in the console. To know that a client has connected and the browser is ready to be controlled.
Workflow:
client.page("name") just like the normal mode to create new pages / connect to existing ones.If the extension hasn't connected yet, tell the user to launch and activate it. Download link: https://github.com/SawyerHood/dev-browser/releases
Run all scripts from
skills/dev-browser/directory. The@/import alias requires this directory's config.
Execute scripts inline using heredocs:
cd skills/dev-browser && npx tsx <<'EOF'
import { connect, waitForPageLoad } from "@/client.js";
const client = await connect();
// Create page with custom viewport size (optional)
const page = await client.page("example", { viewport: { width: 1920, height: 1080 } });
await page.goto("https://example.com");
await waitForPageLoad(page);
console.log({ title: await page.title(), url: page.url() });
await client.disconnect();
EOFWrite to tmp/ files only when the script needs reuse, is complex, or user explicitly requests it.
"checkout", "login", not "main"await client.disconnect() - pages persist on serverpage.evaluate() runs in browser - no TypeScript syntaxFollow this pattern for complex tasks:
Code passed to page.evaluate() runs in the browser, which doesn't understand TypeScript:
// ✅ Correct: plain JavaScript
const text = await page.evaluate(() => {
return document.body.innerText;
});
// ❌ Wrong: TypeScript syntax will fail at runtime
const text = await page.evaluate(() => {
const el: HTMLElement = document.body; // Type annotation breaks in browser!
return el.innerText;
});For scraping large datasets, intercept and replay network requests rather than scrolling the DOM. See references/scraping.md for the complete guide covering request capture, schema discovery, and paginated API replay.
const client = await connect();
// Get or create named page (viewport only applies to new pages)
const page = await client.page("name");
const pageWithSize = await client.page("name", { viewport: { width: 1920, height: 1080 } });
const pages = await client.list(); // List all page names
await client.close("name"); // Close a page
await client.disconnect(); // Disconnect (pages persist)
// ARIA Snapshot methods
const snapshot = await client.getAISnapshot("name"); // Get accessibility tree
const element = await client.selectSnapshotRef("name", "e5"); // Get element by refThe page object is a standard Playwright Page.
import { waitForPageLoad } from "@/client.js";
await waitForPageLoad(page); // After navigation
await page.waitForSelector(".results"); // For specific elements
await page.waitForURL("**/success"); // For specific URLawait page.screenshot({ path: "tmp/screenshot.png" });
await page.screenshot({ path: "tmp/full.png", fullPage: true });Use getAISnapshot() to discover page elements. Returns YAML-formatted accessibility tree:
- banner:
- link "Hacker News" [ref=e1]
- navigation:
- link "new" [ref=e2]
- main:
- list:
- listitem:
- link "Article Title" [ref=e8]
- link "328 comments" [ref=e9]
- contentinfo:
- textbox [ref=e10]
- /placeholder: "Search"Interpreting refs:
[ref=eN] - Element reference for interaction (visible, clickable elements only)[checked], [disabled], [expanded] - Element states[level=N] - Heading level/url:, /placeholder: - Element propertiesInteracting with refs:
const snapshot = await client.getAISnapshot("hackernews");
console.log(snapshot); // Find the ref you need
const element = await client.selectSnapshotRef("hackernews", "e2");
await element.click();Page state persists after failures. Debug with:
cd skills/dev-browser && npx tsx <<'EOF'
import { connect } from "@/client.js";
const client = await connect();
const page = await client.page("hackernews");
await page.screenshot({ path: "tmp/debug.png" });
console.log({
url: page.url(),
title: await page.title(),
bodyText: await page.textContent("body").then((t) => t?.slice(0, 200)),
});
await client.disconnect();
EOF© MemTensor, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 16 other files (scripts, references) in apps/openwork-memos-integration/apps/desktop/skills/dev-browser of MemTensor/MemOS.
Open the folder on GitHubat commit a7367d0
We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in MemTensor/MemOS, which our catalogue first saw on October 7, 2026.
Dev Browser Automation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dev Browser Automation this skillMemTensor/MemOS | 12k | 3 repos | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Core Guide for agent-browservercel-labs/agent-browser | 44k | 4 repos | ~9.5k | Automated safety check: Pass | Apache-2.0 | |
| Browser Control with Omowrightcode-yeongyu/oh-my-openagent | 70k | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Agent Browsernanocoai/nanoclaw | 31k | 3 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Playwright Bowserdisler/bowser | 265 | — | ~1.1k | Automated safety check: Notes | None | |
| Browser Automationynulihao/AgentSkillOS | 617 | — | ~2.2k | Automated safety check: Pass | None |
vercel-labs/agent-browser
Core usage guide for the agent-browser CLI: the snapshot-and-ref workflow for navigating, clicking, filling forms, extracting data and running parallel sessions.
code-yeongyu/oh-my-openagent
Drives a real browser through the omowright library, either the user's own signed-in browser or a separate browser the code launches, for forms, QA, screenshots and scraping.
nanocoai/nanoclaw
Drives a web browser from the shell with the agent-browser CLI: open pages, read an element snapshot, click and fill by reference, grab text and screenshots.
disler/bowser
Headless browser automation using Playwright CLI. An agent skill from disler/bowser.
ynulihao/AgentSkillOS
Non-testing browser automation - web scraping, form filling, screenshot capture, PDF generation, workflow automation.
aiskillstore/marketplace
Browser automation using Playwright MCP. An agent skill from aiskillstore/marketplace.
MemTensor/MemOS
Controls a browser through BrowserWing's local HTTP API: navigation, clicks, typing, data extraction, accessibility snapshots, screenshots and batch operations.
MemTensor/MemOS
Shows a question as a modal in the interface to clarify a task, collect a preference or get approval, since the user cannot see terminal output.
MemTensor/MemOS
Installs, configures and operates BrowserWing, a browser automation platform, covering Chrome setup, LLM provider configuration, and creating or running automation scripts.
MemTensor/MemOS
Enforces explicit user permission before any file deletion. Activates when you're about to use rm, unlink, fs.rm, or any operation that removes files from…
MemTensor/MemOS
Explains when to call MemOS's own memory tools to search past conversations, after the automatic per-turn recall hook comes up empty.
Categories
Automates a real browser through short TypeScript scripts that keep page state between runs, for navigating, filling forms, taking screenshots and extracting data. The skill keeps named pages alive across script executions, so the agent writes small scripts that each do one thing, such as navigate, click, fill or check, and logs state at the end to decide the next step. It picks an approach by situation: read the source of local sites to write selectors directly, use getAISnapshot() and selectSnapshotRef() to find and operate elements on unfamiliar pages, and take screenshots for visual feedback.
Dev Browser Automation fits situations like: navigating a website, clicking through it and filling out forms; taking screenshots of a page to check how it looks; extracting data from a site that needs several steps to reach; testing a local web app by driving it in a browser.
Run `npx skills add MemTensor/MemOS --skill dev-browser -a claude-code`. Or copy the skill folder (apps/openwork-memos-integration/apps/desktop/skills/dev-browser in MemTensor/MemOS) into .claude/skills/dev-browser in your project. Claude Code loads it when a task matches its description.
Run `npx skills add MemTensor/MemOS --skill dev-browser -a codex`. Or copy the skill folder (apps/openwork-memos-integration/apps/desktop/skills/dev-browser in MemTensor/MemOS) into .agents/skills/dev-browser in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MemTensor/MemOS --skill dev-browser -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dev-browser, .gemini/skills/dev-browser, .github/skills/dev-browser and .opencode/skills/dev-browser in your project.
Going by SKILL.md and its folder, Dev Browser Automation needs TypeScript and a shell for the scripts in its folder and the command-line tools its instructions call (npm and npx). Our summary lists: Node.js with npx and tsx; Chromium, or Chrome with the dev-browser extension for extension mode.
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Dev Browser Automation is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Dev Browser Automation: Core Guide for agent-browser (vercel-labs/agent-browser, 44k stars), Browser Control with Omowright (code-yeongyu/oh-my-openagent, 70k stars), Agent Browser (nanocoai/nanoclaw, 31k stars) and Playwright Bowser (disler/bowser, 265 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
MemTensor (a GitHub organization) maintains it in MemTensor/MemOS, which has 11,738 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 29, 2026.
Source: MemTensor/MemOS on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.