Capture website bugs with screenshots and technical context

Overview⁠

OverlayQA lets clients and teammates pin feedback on a live website and captures the screenshot, CSS selector, computed styles, viewport and browser details a developer needs.

Send those issues to Linear one at a time or in bulk, and status, assignee and comments sync back, so the people fixing bugs never leave Linear.

How it works⁠

OverlayQA runs as a Chrome extension on any page your team can open, including localhost and login-gated staging, and as a branded client review link that needs no account. Each pinned issue carries an annotated screenshot, the element’s CSS selector and computed styles, the page URL, viewport size and browser. Automated checks (accessibility audits, AI UI review and Figma comparison) add findings to the same project.

From the dashboard, the extension or a team review, select the issues you want developers to pick up and choose Linear as the destination. OverlayQA creates one Linear issue per selected item, and the screenshot, CSS selector, computed values, viewport and browser details travel with it. The Linear link is recorded on the OverlayQA issue.

Changes in Linear flow back: status, assignee, priority and comments sync to the OverlayQA issue, so clients and designers see progress without a Linear seat. An MCP server also lets AI coding agents read OverlayQA issues and update them when a fix lands.

Configure⁠

Select issues and click Export. Choose Linear as the destination. Click Connect to Linear and authorize with OAuth. Select the Linear team. Click Export to create the Linear issues.

Requirements: an OverlayQA account with write access to the project and a Linear account that can create issues in the chosen team.

Steps with screenshots are available in the OverlayQA docs.