| name | browser-cdp |
| description | Native CDP browser automation reference. Headless/headed Chrome control, screenshots, JS evaluation. (/browser-cdp, browser automation, cdp, scraping) |
Native Browser Automation (CDP)
Built-in browser control via Chrome DevTools Protocol — no Node.js, no Playwright, pure Rust.
Tools
| Tool | Required | Optional | What |
|---|
browser_navigate | url | headless | Navigate to URL |
browser_click | selector | — | Click element by CSS selector |
browser_type | text | selector | Type text into input |
browser_screenshot | — | selector | Screenshot (returns file path) |
browser_eval | script | — | Execute JavaScript |
browser_content | — | selector, text_only | Extract text/HTML |
browser_wait | — | selector, timeout_secs, delay_secs | Wait for element or delay |
browser_find | pattern | mode, limit | Find elements on page |
Headless vs Headed
- Headless (default): No visible window. Fast, low resources.
- Headed: Visible Chrome window. Pass
headless: false to browser_navigate.
Usage Tips
- Compose workflows: navigate → wait → click → type → screenshot
- Screenshots return file paths. Use
<<IMG:path>> to send to channels.
- JavaScript evaluation for complex DOM manipulation and SPAs.
- No credentials stored. Navigate to login page and use click/type for auth (with user approval).
- Requires Chrome/Chromium installed. Feature-gated:
browser flag.
Chrome Launch Failures
- SingletonLock exists:
rm -f ~/.opencrabs/chrome-profile/SingletonLock ~/.opencrabs/chrome-profile/SingletonCookie ~/.opencrabs/chrome-profile/SingletonSocket then retry.
- DevTools data dir conflict:
pkill -f chrome then retry.
- Channel closed: Kill Chrome, delete lock files, retry.
