OpenErrand
OverviewDocsllms.txt
Get startedQuickstartIntegration Guide — zero to first taskAuthor a playbook with an LLM coding toolQuickstart: driving a task with an LLM
How it worksOBEP Security ModelThe Open/Closed Boundary (OBEP vs OpenErrand)OBEP Error Taxonomy
Run & deploySelf-Hosting an OBEP RelayEnterprise Deployment (force-install + managed config)
Trust & legalOpenErrand — Privacy Policy

OpenErrand documentation

A universal, safe way to run actions in a real browser — for yourself, or for your users. Start with the quickstart; everything else is here when you need it.

Get started

QuickstartThe easiest way to add OpenErrand is to let your AI coding tool set it up. Integration Guide — zero to first taskThis is the developer front door — for a product that wants to run a browser action for Author a playbook with an LLM coding toolThe fastest way to write a playbook is to let your coding assistant (Claude Code, Cursor, Quickstart: driving a task with an LLMOpenErrand is "the pipe" — you bring the intelligence.

How it works

OBEP Security ModelThis document states the trust model plainly so a customer's security team can The Open/Closed Boundary (OBEP vs OpenErrand)Governing rule: anything whose secrecy would create a vulnerability MUST be OBEP Error TaxonomyStable error codes carried on status messages (phase: "error", code).

Run & deploy

Self-Hosting an OBEP RelayOBEP is self-hostable: the reference relay in obep/relay-reference Enterprise Deployment (force-install + managed config)Force-install via Google Workspace admin policy is the primary B2B distribution

Trust & legal

OpenErrand — Privacy PolicyLast updated: 2026-06-15

Reading this as a machine? Grab /llms.txt · /llms-full.txt — or any page as /docs/<name>.md.