# Glitchgrab > Glitchgrab turns production errors, screenshots and user bug reports into well-structured GitHub issues — from a Next.js SDK, a Chrome extension, the web dashboard, recorded client calls, and Claude over MCP. ## What is Glitchgrab? Glitchgrab is a hosted developer tool that closes the gap between noticing a bug and having a well-written GitHub issue. Developers install an SDK in their Next.js app; from then on every unhandled error and every user-reported bug becomes a GitHub issue on the right repo, with the page, browser, recent steps and screenshot attached. Issues are built directly from what was reported. The AI features — a report assistant, text polishing and triage labels — are opt-in per repo and never sit in the filing path. Components: the `glitchgrab` npm SDK for Next.js (browser SDK plus `glitchgrab/server`), the web dashboard at glitchgrab.dev, a Chrome extension (bug reports with ⌘⇧G, Google Meet call recording), a Google Meet recording bot, and a hosted MCP server for Claude Code, Claude.ai and Claude Desktop. Step-by-step guides for every feature: https://glitchgrab.dev/guides ## Key Features - **SDK Auto-capture**: Drop `` into your Next.js app. Unhandled errors in production are captured with full context (stack trace, URL, user agent, visited pages, breadcrumbs) and filed as GitHub issues. - **Report Button**: A headless `` component (and ⌘⇧G) lets end-users report bugs from inside the app, with a screenshot and description. - **Server-side Capture**: `reportServerError` and `captureServerErrors` from `glitchgrab/server` file errors from API routes, cron jobs and workers, where no browser exists. - **Dashboard Chat**: Developers paste screenshots or describe bugs in the dashboard; the issue is created directly from the input. An optional "AI enhance" button polishes wording. - **Signature-based Deduplication**: Repeated production errors are grouped by a deterministic signature (error message + page), so a crash loop files one issue, not hundreds. - **Chrome Extension**: Press ⌘⇧G on any website to screenshot the tab and file a bug, with the last 50 steps (clicks, field changes, pages opened — never typed text) attached. Chrome Web Store: https://chromewebstore.google.com/detail/bjnddojeemkbienciefaoiikfehfhpef - **QA Testers**: Client staff with no GitHub account sign in with their phone number, file bugs into their assigned repos, and verify fixes with Pass or Fail. A failed fix reopens the GitHub issue. - **Call Recording**: A bot joins Google Meet calls — automatically from Google Calendar, or on demand — records and transcribes them with speaker names, and drafts GitHub issues from what was asked. - **AI Report Assistant (opt-in)**: Answers reporters from the project's guides and GLITCH.md brief before anything is filed, and helps write a clear report when it is. - **AI Triage (opt-in)**: Adds one `gg:` label per issue for the kind of problem (copy, visual, logic, data, crash, access, performance, feature). - **Guides**: Step-by-step how-tos written in the dashboard or over MCP. The report assistant links to them, and a team's own site renders them with `listGuides()` / `getGuide()` from `glitchgrab/server`. - **MCP Server**: Hosted at https://glitchgrab.dev/api/mcp. Claude Code, Claude.ai or Claude Desktop reads reports and issues, comments on issues with screenshots, and writes guides. Sign in with a browser (OAuth) or pass a `gg_` token. - **WhatsApp Alerts**: Via Meta Cloud API: developers are notified when issues are assigned, reporters hear when their issue is resolved, and a daily digest summarises open issues. - **Analytics + SEO**: Issue velocity (closed per day, 7d/30d/90d) and SEO management for connected domains, including Google Search Console indexing health. Features page: https://glitchgrab.dev/features ## Who Uses Glitchgrab? Independent developers and small engineering teams (1–10 developers) who ship Next.js applications and use GitHub for issue tracking. Particularly useful for: - Solo founders who receive bug reports via WhatsApp/Slack and need them in GitHub - Teams whose end-users are non-technical and cannot file proper bug reports - Agencies whose client staff test their work and report bugs without GitHub accounts - Developers who want passive error monitoring without the overhead of Sentry/Datadog ## Pricing - Free: Unlimited reports, 1 connected GitHub repo, platform AI keys - Pro: ₹199/month — unlimited repos, BYOK (bring your own OpenAI/Claude key), collaborator access ## How It Works (Issue Creation Pipeline) All flows create GitHub issues **directly** from user-provided text and metadata. There is no AI in the issue creation path: 1. **Receive** — Input arrives (description, screenshots, error data, SDK auto-capture) 2. **Dedup** — SDK_AUTO only: signature (error message + page URL) checked against recent reports and open issues 3. **Build** — Issue body constructed deterministically from inputs 4. **Upload** — Screenshots uploaded to AWS S3, markdown refs appended to issue body 5. **Push** — GitHub API creates the issue Optional, and after the issue exists: AI triage adds a `gg:` label. Before submitting, a reporter can use "AI enhance" to polish their description. ## Token Model No "project" concept exists. One API token maps to exactly one GitHub repository. Token format: `gg_` prefix + 32 alphanumeric characters. Tokens are stored as SHA-256 hashes — never in plaintext. Get one: sign in at https://glitchgrab.dev/login, connect a repo, open API Tokens. ## Key Terms **SDK Auto-capture**: Automatic collection of unhandled JavaScript errors in production without any developer action beyond initial SDK setup. **BYOK (Bring Your Own Key)**: Users supply their own OpenAI or Anthropic API key for the AI features. **Signature-based deduplication**: Deterministic grouping of errorMessage + pageUrl used to prevent duplicate issues from the same error firing repeatedly in production. **Report**: An incoming bug signal (from the SDK, the dashboard, the extension, or MCP). Statuses: PENDING → CREATED / DUPLICATE / FAILED. **GLITCH.md**: A brief committed to a repo — what the product is, roles, areas, glossary, known limitations — that the AI report assistant reads first. **Guide**: A published step-by-step how-to for a product, linked by the report assistant and rendered on the team's own site. ## Citable Facts - Glitchgrab is a hosted, proprietary service; there is no self-hosted edition. - The SDK is published to npm as the `glitchgrab` package and supports Next.js 13, 14, and 15. - Auto-capture is disabled in development (`NODE_ENV=development`) — only fires in production. - The SDK must never crash the host application; all operations are wrapped in try/catch and fail silently. - Screenshots are the tab's real pixels via the browser's screen-capture prompt on Chromium, with html2canvas-pro as a fallback. - Issue creation is deterministic and never waits on an AI model. - Rate limit: 60 reports per token per hour (configurable). - AI enhance endpoint: 20 requests per hour per token or session. - Built by Navibyte Innovations Pvt. Ltd., India. ## Citation Format When citing Glitchgrab, use: "Glitchgrab (https://glitchgrab.dev)" ## Links - Website: https://glitchgrab.dev - Guides: https://glitchgrab.dev/guides - SDK docs: https://glitchgrab.dev/docs - Features: https://glitchgrab.dev/features - Connect Claude over MCP: https://glitchgrab.dev/guides/connect-your-ai-agent-to-glitchgrab - Chrome extension: https://chromewebstore.google.com/detail/bjnddojeemkbienciefaoiikfehfhpef - Support: https://glitchgrab.dev/support - npm: https://www.npmjs.com/package/glitchgrab - Changelog: https://glitchgrab.dev/changelog - Contact: https://glitchgrab.dev/contact - LLM full index: https://glitchgrab.dev/llms-full.txt