Bug Reports Delivered as GitHub Issues
Callout captures annotated screenshots, console errors, and device details — then delivers them directly as GitHub Issues. No copy-paste, no context switching.
Three steps to
better bug reports.
From user report to GitHub Issue in seconds — fully automatic.
User reports a bug
A tester or team member clicks the Callout widget, annotates the screenshot with arrows and highlights, and adds a description. Takes under 30 seconds.
Callout captures everything
Behind the scenes, Callout automatically captures console errors, browser and OS details, viewport size, the current page URL, and session replay links if available.
GitHub Issue created
Callout creates a fully formatted GitHub Issue in your repository with the annotated screenshot, all captured details, and the user description. Ready for your team to triage.
Every issue, fully
detailed.
No more “it's broken” issues. Every report includes everything your team needs.
Annotated screenshot
Full-page screenshot with arrows, boxes, and highlights drawn by the reporter. Uploaded to GitHub and embedded directly in the issue body.
Console errors
JavaScript errors and warnings captured automatically at the moment of report. No need to ask the reporter to open DevTools.
Browser & OS details
Browser name and version, operating system, and viewport dimensions. Helps you reproduce environment-specific bugs immediately.
Page URL
The exact URL where the bug was reported, including path and query parameters. No guessing which page the user was on.
Session replay link
If PostHog, LogRocket, Hotjar, or FullStory is detected on the page, Callout automatically attaches the session replay link to the issue.
60-second
install.
No npm packages, no build steps, no browser extensions. Just a PAT and a script tag.
Get started in three steps
- Create a GitHub Personal Access Token (PAT) with reposcope. Go to GitHub Settings → Developer Settings → Personal Access Tokens → Generate New Token.
- Paste your PAT into the Callout dashboard along with your repository owner and name. Callout encrypts and stores the token securely.
- Copy the single script tag from the dashboard and add it to your site. Bug reports will start appearing as GitHub Issues immediately.
Common
questions.
Does Callout work with any GitHub repository?
Yes. Callout works with any public or private GitHub repository. You provide a Personal Access Token (PAT) with repo scope during setup, and Callout creates issues in whichever repository you configure. There are no restrictions on organization type or plan.
What information is included in each GitHub Issue?
Every GitHub Issue created by Callout includes an annotated screenshot, console errors captured automatically, browser and OS details, viewport dimensions, the page URL where the bug was reported, and a session replay link if a supported replay tool like PostHog is detected.
How long does it take to set up the GitHub integration?
Under 60 seconds. You create a GitHub Personal Access Token with repo scope, paste it into the Callout dashboard, add a single script tag to your site, and you are done. No npm packages, build steps, or browser extensions required.
Is the GitHub Personal Access Token stored securely?
Yes. Your GitHub PAT is encrypted at rest and is only used server-side to create issues on your behalf. The token is never exposed to the browser or included in the widget code. Callout uses the token solely to call the GitHub API when a bug report is submitted.
Start delivering bug reports as GitHub Issues
Free forever. No account required. Set up in under a minute.
Get Started Free