Technical architecture with deterministic surfaces

OpenDevBrowser combines a script-first runtime, extension relay, and diagnostics stack into one implementation-ready architecture.

Runtime architecture map

Browser manager, relay, tools, and workflow modules operate as composable layers.

Managed mode

Launch and control a managed browser process with deterministic lifecycle handling.

Extension ops mode

Operate inside logged-in browser contexts through extension relay surfaces.

Legacy CDP mode

Attach to pre-existing debuggable sessions when lower-level control is required.

Tool surface

48 tool endpoints cover navigation, interaction, DOM, diagnostics, export, and workflow surfaces.

CLI surface

55 commands provide script-first operational control and daemon-backed execution.

Verification surfaces

Status, traces, logs, and metrics provide confidence gates for each automation run.

Mode comparison

Choose the right runtime mode for each execution context without changing tool semantics.

Managed

Full lifecycle control with isolated browser process management and deterministic startup behavior.

launch --no-extension

Extension ops

Operate in existing logged-in tabs through relay channels and policy-aware controls.

launch --extension-only

Legacy CDP

Direct CDP attachment path for integration with existing remote debugging setups.

connect --extension-legacy

Tool surface clusters

Feature domains are grouped for predictable implementation paths.

Navigation and interaction

goto, snapshot, click, type, select, scroll, and wait flows.

DOM and extraction

HTML, text, attr/value/state inspection for deterministic extraction logic.

Diagnostics

console, network, trace snapshots, and perf surfaces for regression analysis.

Export and artifact

screenshot, clone page/component, annotate, and rich output pipelines.

Macro and orchestration

macro resolve and workflow wrappers for reusable automation sequences.

Session and targets

launch/connect/status and page/target management controls.

Diagnostics and verification surfaces

Regression-safe operations require observable state at every stage of execution.

diagnostics.sh
opendevbrowser status
opendevbrowser console-poll
opendevbrowser network-poll
opendevbrowser debug-trace-snapshot
opendevbrowser perf

Verification model

Each claim on the landing surface maps to source files, command surfaces, and testable runtime behavior.

runtime + tests + observable outputs

Export and artifact surfaces

Capture outputs for QA, reports, and downstream automation loops.

Screenshots

Collect visual evidence from deterministic browser states.

Clone page/component

Extract reusable front-end structures from live DOM state.

Annotation

Capture structured review metadata with screenshot artifacts.

Workflow integration block

Connect low-level action controls with high-level business workflows.

Composable flow

Launch/action tools feed research, shopping, and product-video wrappers through one deterministic contract.

Policy-aware execution

Per-run cookie controls and structured diagnostics (`auth_required`, `cookieDiagnostics`) keep auth-sensitive workflows predictable.

Go from architecture to execution

Dive into docs for implementation details, command references, and operation patterns.