| name | Vibe Check - Browser Automation |
| description | Browser automation for AI agents. Navigate pages, fill forms, click elements, take screenshots, and manage tabs — all through simple CLI commands. 2.6k+ GitHub stars. |
| version | 1.0.0 |
| author | vibiumdev |
| license | MIT |
| tags | ["browser-automation","vibe-coding","ai-agent","chrome","cli","testing","web-scraping"] |
| testingTypes | ["e2e","visual","accessibility"] |
| frameworks | ["playwright"] |
| languages | ["typescript","javascript","python","go"] |
| domains | ["web","mobile"] |
| agents | ["claude-code","cursor","github-copilot","windsurf","codex","aider","continue","cline","zed","bolt","opencode","gemini-cli","amp"] |
Vibium Browser Automation — CLI Reference
The vibium CLI automates Chrome via the command line. The browser auto-launches on first use (daemon mode keeps it running between commands).
vibium go <url> && vibium map && vibium click @e1 && vibium map
Core Workflow
Every browser automation follows this pattern:
- Navigate:
vibium go <url>
- Map:
vibium map (get element refs like @e1, @e2)
- Interact: Use refs to click, fill, select — e.g.
vibium click @e1
- Re-map: After navigation or DOM changes, get fresh refs with
vibium map
Binary Resolution
Before running any commands, resolve the vibium binary path once:
- Try
vibium directly (works if globally installed via npm install -g vibium)
- Fall back to
./clicker/bin/vibium (dev environment, in project root)
- Fall back to
./node_modules/.bin/vibium (local npm install)
Run vibium --help (or the resolved path) to confirm. Use the resolved path for all subsequent commands.
Windows note: Use forward slashes in paths (e.g. ./clicker/bin/vibium.exe) and quote paths containing spaces.
Command Chaining
Chain commands with && to run them sequentially. The chain stops on first error:
vibium go https://example.com && vibium map && vibium click @e3 && vibium diff map
When to chain: Use && for sequences that should happen back-to-back (navigate → interact → verify). Run commands separately when you need to inspect output between steps.
When NOT to chain: Don't chain commands that depend on parsing the previous output (e.g. reading map output to decide what to click). Run those separately so you can analyze the result first.
Commands
Discovery
vibium map — map interactive elements with @refs (recommended before interacting)vibium map --selector "nav" — scope map to elements within a CSS subtree- — compare current vs last map (see what changed)
