OpenDevBrowser Relay
Optional bridge to reuse existing Chrome tabs with OpenDevBrowser.
As of June 2026, OpenDevBrowser Relay has — users in the Developer Tools category.
Usersno change0%
—
—
Ratingno change0%
—
— reviews
Reviewsno change0%
—
Version
0.0.34
Manifest V3
90-day change · In the last 90 days this extension 4 version updates, changed permissions.
History
5 snapshotsTracking since Apr 16, 2026.
Not enough history yet for this metric — the chart fills in as we collect more snapshots.
View as table
| Date | Users | Rating | Reviews | Version |
|---|---|---|---|---|
| Apr 16, 2026 | — | — | — | 0.0.17 |
| Apr 22, 2026 | — | — | — | 0.0.17 |
| Apr 27, 2026 | — | — | — | 0.0.24 |
| May 21, 2026 | — | — | — | 0.0.26 |
| May 27, 2026 | — | — | — | 0.0.31 |
| Now | — | — | — | 0.0.34 |
Changelog
- Apr 22, 2026description
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, and capture annotations without launching a separate browser. What it delivers: - 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 - 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 - 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
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
- Apr 22, 2026permissions
debugger, alarms, tabs, storage, scripting, activeTab, nativeMessaging
debugger, webNavigation, alarms, tabs, storage, scripting, activeTab, nativeMessaging
Permissions & access
- Permissions
- debuggerwebNavigationalarmstabsstoragescriptingactiveTabnativeMessaging
- Host access
- http://127.0.0.1/*, <all_urls>
Screenshots
About
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
Technical
- Version
- 0.0.34
- Manifest
- V3
- Size
- 175KiB
- Min Chrome
- 88
- Languages
- 1
- Featured
- No
Metadata
- ID
- mfajibjdacmecipgcpnagccbieabglhk
- Developer ID
- u397d4aea00ae7a1146e8261f4f639379
- Developer Email
- [email protected]
- Created
- Mar 5, 2026
- Last Updated (Store)
- May 22, 2026
- Last Scraped
- Jun 9, 2026
- Website
- —
Similar extensions
Alternatives to OpenDevBrowser Relay, ranked by description similarity.
OpenClaw Browser Relay
Attach OpenClaw to your existing Chrome tab via a local CDP relay server.
5.0K
★ 2.6
Relay – Intercept, Modify & Run HTTP Requests in Your Browser
Intercept, edit, and run HTTP requests directly in your browser. No account needed.
996
★ 5.0
CheckFlow Browser Relay
Connect your AI agent to Chrome. Automate browsing, extract data, fill forms — 100% local, no cloud. Powered by CheckFlow.
2.0K
★ 2.0
ClawHosters Browser Relay
Connect your ClawHosters OpenClaw instance to your browser tabs for AI-powered browser automation
48
shareq.site
Capture and share HTTP requests from Chrome DevTools
—
dom0
Browser automation for AI agents
43
DOMShell — Browser Filesystem for AI Agents
Browse the web with Linux commands. AI agents use ls, cd, grep, click via MCP. Terminal in Chrome Side Panel.
591
OpenClaw Browser Relay for Windows
Local relay bridge to attach OpenClaw to your existing Chrome tab on Windows.
6.0K
★ 3.0
Data sourced from the Chrome Web Store · last verified Jun 9, 2026.