Vibium Docs

Start here

Read the Introduction for the elevator pitch, or jump straight to the Quickstart to run three commands.

Build a mental model

Getting Started walks through the moving parts. Core Concepts explains the design.

Worked example

The Tutorial fills out a real form end-to-end.

Reference

Browse the Command Reference and the Client Libraries overview.

What Vibium does

Vibium gives an agent or script a real browser session with a compact command surface. The usual loop is to open a page, map the interactive elements, choose the right reference, act on that element, then read back the visible state. The same session can produce screenshots, PDFs, extracted text, and recordings, so the browser state is useful both to humans reviewing a run and to agents planning the next step.

The documentation is organized around that loop. Start with installation when you need the binary and browser runtime, use the quickstart for a short live run, then move to the tutorial when you want a complete form-filling workflow. The command reference is intentionally direct: each page explains one command, its arguments, and a small example that can be copied into an agent or shell session.

Terminology and concepts

The Core Concepts page is the glossary-style reference for the terms used throughout these docs. It explains browser sessions, element references, maps, diffs, waits, assertions, captures, and recordings. Those terms appear in the CLI reference, the MCP integration guide, and the client library overview, so keeping the vocabulary explicit helps agents navigate the site without guessing from surrounding prose.

Agent-readable docs

The site publishes multiple machine-readable entrypoints. /llms.txt is the curated index of clean Markdown sources, /llms-full.txt is the expanded single-file context document, and /llms/ contains the source Markdown files linked by the index.