The language of agentic browser automation
Definition-first explanations of the concepts behind Twin Browser and the broader field — from the semantic dispatch cache that bends the cost curve to the credential vault that keeps authenticated runs safe.
Browse the glossary
Each entry is a short, citable definition plus why it matters for running agents over the browser at volume.
Semantic dispatch cache
A vector cache that matches a new, re-phrased request to a skill you already compiled — so a repeated task skips the LLM.
Deterministic replay
Re-running a compiled skill as a fixed sequence of indexed actions, with zero LLM calls, so the same goal produces the same path every time.
Skill compilation
Turning a successful agent run into a reusable, replayable skill — a compact program of indexed actions you can call again without re-planning.
DOM indexed state
A compact, numerically-indexed map of a page’s interactive elements that an agent acts on by index instead of raw HTML.
Cross-tenant skill corpus
A shared, sanitized library of compiled skills that lets a skill compiled once be safely reused across tenants, compounding the cache savings.
Human-in-the-loop handoff
Pausing a run at a step that needs a person — an approval or an MFA prompt on an authorized flow — then resuming automatically once it’s cleared.
Browser execution layer
The infrastructure that turns an agent’s goal into deterministic, replayable browser action — the layer between your LLM and a real browser.
Token-efficient DOM
A page representation stripped to just the interactive, indexed elements under a token budget — so prompts stay small and cheap.
MCP server
A Model Context Protocol endpoint that exposes Twin as agent tools (run, compile_skill, run_skill) to MCP clients like Cursor, Claude Desktop, Claude Code, and Cline.
Headless vs headful
Headless runs a browser with no visible UI; headful runs a real, rendered browser. The choice affects compatibility, observability, and how some sites behave.
RPA vs agentic automation
RPA follows brittle, hand-recorded scripts; agentic automation has a model plan against the live page — then compiles the result so it can replay cheaply.
Session video
A durably-stored recording of a browser run, plus real-time live view — so every automated session is watchable and auditable after the fact.
Credential vault
Encrypted per-tenant storage for the secrets a run needs — logins and tokens — injected at execution time and never exposed to the model or other tenants.
Marginal cost per run
The cost of one more execution of a workflow. On most browser infra it’s flat; on Twin it falls as cache hits replace LLM calls.
Stop paying the model on every run.
Compile a workflow once, then let the semantic cache and deterministic replay serve the repeats. Marginal cost trends toward zero as you scale.