LayerDock
GitHub integration

Visual bug reports from your site, opened as GitHub issues.

A reviewer clicks the broken thing and says what is wrong. Layerdock opens an issue in the repository you chose, with the screenshot, the selector and the browser it happened in.

Setup guide
At a glance

What you get in GitHub

A pin becomes
An issue labelled layerdock, in the repository you pick for that dock
The issue carries
The comment, the screenshot, the page URL, CSS selector, viewport, and the reporter’s browser and OS
Status sync
Two-way: closing the issue resolves the pin, reopening it reopens the pin
Connects by
A GitHub App, installed on only the repositories you select
Access to GitHub
Issues only. The app never reads code
Plans
Pro and Agency
Setup

Connect GitHub in three steps

The GitHub setup guide has every screen and what to do if something goes wrong.

  1. Step 1

    Install the GitHub App

    From Integrations, choose GitHub and the dock. GitHub asks which account to install into; pick “Only select repositories” and choose the ones Layerdock may use.

  2. Step 2

    Choose a repository

    Back in Layerdock, pick the repository this dock files into. The list is fetched live, and archived repos or repos with issues turned off are hidden.

  3. Step 3

    Send a test

    Press Test and an issue appears within a few seconds, labelled layerdock so it is easy to filter.

Good to know

How it behaves

A GitHub App, not somebody’s token

A personal access token stops working when its owner leaves or it expires. The App keeps working, and its reach is limited to issues on the repositories you picked.

The screenshot is a link

GitHub has no public API for attaching a file to an issue, so the image is embedded from Layerdock. It renders in the issue like any other image.

One repository per dock

Each dock files into its own repository, so the marketing site and the web app do not share an issue list unless you want them to.

Works alongside a coding agent

The same pin can be read over MCP by Claude Code, Cursor and other agents, with the console and network trace, then resolved from the editor.

Ready when you are

Make the next
website review easier.

Give your team and clients one clear place to see the issue, capture the context, and share the fix.

Explore the tools
FAQs

Frequently asked questions

What to know before connecting GitHub.

Does Layerdock get access to my source code?

No. The GitHub App only reads and writes issues, and only on the repositories you select when installing it.

Does closing the GitHub issue close the feedback?

Yes, once the repository webhook from the setup guide is added. Closing the issue resolves the pin; reopening it moves the pin back to open.

Do clients need a GitHub account?

No. Clients comment from a review link with no account. The issue is opened by the Layerdock app.

Can I connect a private repository?

Yes. Select it when installing the GitHub App. The repository must not be archived and must have issues enabled.

Which Layerdock plans include integrations?

Pro ($19/mo) and Agency ($69/mo), both per workspace with unlimited reviewers. The Free plan does not include outbound integrations.