browser

Vibium Browser Automation — CLI Reference

The vibium CLI automates Chrome (and Firefox, via --engine firefox) from the command line. The browser auto-launches on first use (daemon mode keeps it running between commands).

Use this skill for browser automation, exploration, debugging, and recording. Choose explicit CLI commands when you know the steps, or use vibium run when a model should work out how to accomplish a browser goal.

For an independent acceptance verdict, use the check skill if installed, or vibium check "<claim>". Run’s completed result and your own browser observations do not substitute for that invocation.

Core Workflow

For direct browser commands, use this pattern:

1. Navigate: vibium go <url>
2. Map: vibium map (get element refs like @e1, @e2)
3. Interact: Use refs to click, fill, select — e.g. vibium click @e1
4. 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:

1. Try vibium directly (works if globally installed via npm install -g vibium)
2. Fall back to ./clicker/bin/vibium (dev environment, in project root)
3. 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.

Browser readiness

During initial setup, run vibium ready browser --json with the engine/channel that the workflow will use. It inspects installed browser and driver files without launching them or touching existing sessions. Passing confirms the installation, not browser launch or BiDi connectivity. If installation is missing, use the reported vibium install command and retry. Direct browser work does not need AI configuration. Do not rerun readiness before every action when setup is unchanged.

Delegate a browser goal with Run

Use vibium run "<goal>" when the task is clear but the sequence of browser actions needs investigation. For known steps, use the commands below directly. Run uses the existing local Chrome or Firefox session and a fresh model context. Keep the same --session or VIBIUM_SESSION throughout the workflow.