BrowserQA Copilot Bridge

About

BrowserQA Copilot Bridge connects your BrowserQA account to normal websites while you test. Pick elements on the live page, turn them into concise UI context for Copilot, and drive your BrowserQA workflow—without leaving Chrome.

What you can do

Open the side panel from the toolbar to pick elements on the page and build a queued list of UI captures sent to BrowserQA Copilot as structured context.
Attach manual test cases from your BrowserQA project to push toward Playwright-ready automation.
Generate manual test case drafts from picked UI plus optional notes when no case is attached.
Use in-page Copilot: a launcher on the tab lets you show or hide a Copilot surface on the site; messages use the same project, picks, and optional notes from the sidebar.
Sign in with BrowserQA via Chrome identity, or fall back to a pairing code flow when supported.
Why install it

Bridges real-product pages with BrowserQA’s Copilot APIs (/api/copilot/chat): less copy-paste, fewer dropped selectors, tighter loop between exploratory QA and test management.
Hosts & permissions

Access to HTTPS/HTTP origins powers the picker, injected Copilot widget, tab metadata, and server calls. Sensitive pages Chrome blocks (e.g. chrome://, extension store chrome) cannot be scripted; the UI explains that when Pick fails.
Identity opens BrowserQA sign-in; tabs / activeTab / scripting target the focused tab safely; side panel ships the companion UI; storage keeps tokens, picks, project, and conversation-linked state locally.
Requires an active BrowserQA account at the service you configured (typically browserqa.io).