dev-browser
Automate website navigation, form filling, screenshots, data extraction, and web app testing in Chrome through the dev-browser CLI. Named pages persist between runs, allowing browser tasks to continue across separate script executions.
OriginalShow the original description
Browser automation with persistent named pages via the dev-browser CLI. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, log into sites, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", "open the browser", or any browser interaction request.
Good for
- Automating website navigation and form entry
- Saving screenshots of web pages
- Extracting information from websites
- Checking web app behavior and login flows
Files included (1)
- SKILL.md1.8 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
dev-browser
CLI for controlling a real Chrome with short Puppeteer scripts. One warm daemon; named pages persist between runs.
npm install -g dev-browser # bun add -g dev-browser works too; the first run downloads the binary if the install script was blocked
dev-browser install # only if the first run says "No Chrome found"
Run dev-browser --help (full guide; dev-browser help <topic> for one section) before non-trivial work. Quick start:
dev-browser <<'EOF'
const page = await browser.getPage("main"); // named page persists across runs
await page.goto("https://example.com"); // default waitUntil: domcontentloaded
await page.snapshot({ interactive: true }) // ARIA tree with refs; last expression is printed
EOF
dev-browser -e 'const p = await browser.getPage("main"); await p.click("ref/e6"); await p.waitForLoad(); p.url()'
Gotchas: end lines with semicolons (a line starting with ( continues the previous one); return an object as
({ a, b }); page.click never waits (use waitForSelector first); page names are per browser (--headless and
headed are separate Chromes and profiles); refs reset on navigation — re-snapshot; file paths resolve against your cwd
(uploadFile, screenshot/pdf path); do not run parallel dev-browser calls against the same named page.
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.