Technical architecture with deterministic surfaces
OpenDevBrowser combines managed, extension, and CDP connect modes with browser replay, desktop observation, and browser-scoped computer use in one implementation-ready architecture.
OpenDevBrowser combines managed, extension, and CDP connect modes with browser replay, desktop observation, and browser-scoped computer use in one implementation-ready architecture.
Browser manager, relay, tools, and workflow modules operate as composable layers.
Launch and control a managed browser process with deterministic lifecycle handling.
Operate inside logged-in browser contexts through extension relay surfaces.
Open extension-hosted design tabs, overlays, preview refresh loops, and TSX-first repo code sync from one public surface.
70 tool endpoints cover navigation, interaction, DOM, diagnostics, export, canvas, and workflow surfaces.
77 commands provide script-first operational control across runtime, relay, workflow, and canvas surfaces.
Status, traces, logs, and metrics provide confidence gates for each automation run.
The generated help surface now exposes the exact operator labels for replay, desktop observation, and browser-scoped computer use.
Use the public browser replay lane when you need temporal browser evidence before or after a fragile flow.
Use the public read-only desktop observation plane for sibling desktop evidence on macOS; availability, window inventory, and accessibility probes use the local swift command, while screenshots use macOS screencapture outside extension relay.
Control the bounded browser-scoped computer-use challenge lane with --challenge-automation-mode; the optional helper is not a desktop agent.
Choose the right runtime mode for each execution context without changing tool semantics.
Full lifecycle control with isolated browser process management and deterministic startup behavior.
Operate in existing logged-in tabs through relay channels and policy-aware controls.
Direct CDP attachment stays available for remote debugging and deterministic browser handoff flows.
Feature domains are grouped for predictable implementation paths.
goto, snapshot, click, type, select, scroll, and wait flows.
HTML, text, attr/value/state inspection for deterministic extraction logic.
console, network, trace snapshots, and perf surfaces for regression analysis.
screenshot, clone page/component, annotate, and rich output pipelines.
macro resolve and workflow wrappers for reusable automation sequences.
launch/connect/status plus design-tab preview, feedback events, and repo-backed code-sync controls.
Regression-safe operations require observable state at every stage of execution.
opendevbrowser status opendevbrowser console-poll opendevbrowser network-poll opendevbrowser debug-trace-snapshot opendevbrowser perf
Each claim on the landing surface maps to source files, command surfaces, and testable runtime behavior.
Capture outputs for QA, reports, and downstream automation loops.
Collect visual evidence from deterministic browser states.
Extract reusable front-end structures from live DOM state.
Capture structured review metadata with screenshot artifacts.
Connect low-level action controls with high-level business workflows.
Launch/action tools feed research, shopping, and product-video wrappers through one deterministic contract.
Per-run cookie controls and structured diagnostics (`auth_required`, `cookieDiagnostics`) keep auth-sensitive workflows predictable.
Dive into docs for implementation details, command references, and operation patterns.