4 items
Optional bridge to reuse existing Chrome tabs with OpenDevBrowser. OpenDevBrowser Relay connects OpenDevBrowser to the Chrome tabs you already have open. It lets the runtime attach to a real headed browser session, reuse logged-in state, inspect the page, drive actions, capture annotations, and participate in local browser replay capture without launching a separate browser. Generated help in the public package also surfaces adjacent runtime lanes for browser replay, public read-only desktop observation, and browser-scoped challenge handling. This extension participates in the relay-backed browser lane only; it is not a desktop agent. What it delivers today: - Reuses existing Chrome tabs through a local relay on `127.0.0.1` - Attaches Chrome DevTools Protocol with `debugger` for inspect and action loops - Injects page-side helpers with `scripting` for annotation, DOM capture, and in-tab automation - Participates in user-triggered local browser replay capture through the existing screenshot lane - Stores relay settings plus the last local annotation payload metadata so the popup can reconnect and reopen recent results - Shows relay, handshake, annotate, injected, `CDP`, pairing, and native fallback health directly in the popup Important behavior notes: - The relay and optional native host stay on-device - OpenDevBrowser does not send browsing data, page content, or annotation payloads to the developer or third-party analytics services - Browser replay manifests, preview images, and sampled frames stay on-device in the chosen output directory - Public desktop observation is a separate read-only core runtime lane and is not provided by this extension - Bounded challenge automation remains browser-scoped and does not turn the extension into a desktop-control surface - The extension can act on user-opened sites because it needs `<all_urls>` for automation, annotation, DOM capture, and screenshot fallback - Restricted pages such as `chrome://`, `chrome-extension://`, and Chrome Web Store pages are not supported targets
Jul 3, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.