Bugmint · TCC intake for product teams

The structured front door for everything your team gets asked to ship.

QA, PMs, support, designers — anyone who notices something — captures it once. Bugmint classifies, dedupes, and routes the ticket to the right repo, channel, or coding agent. The translation layer disappears.

Start free — 10 repos How it works

How it works

One inbox, four sane steps.

Capture from anywhere. Triage in one place. Hand off to humans or agents. Close the loop without drift.

Step 01 · Capture

One sentence + the page.

Chrome extension, embedded widget, or a quick API call. Console logs, network trace, screenshot, and DOM selector ride along automatically.

Step 02 · Classify

Bug, feature, copy, chore, question.

An LLM tags the type, drafts a clean title, extracts trace IDs, and dedupes against open tickets. The reporter stays in flow.

Step 03 · Route

Per-rule, per-trigger.

Bugs to a repo. Copy changes to Slack. Questions stay in the inbox. Routing rules fire on capture, on triage, or never — your call.

Step 04 · Hand off

Human or agent. Same artifact.

Engineers grab tickets from the dashboard. Coding agents (Claude Code, Cursor, Codex) grab them via MCP. PR merges flip status to done automatically.

Features

Everything you need. Nothing you don't.

Bugmint is opinionated on purpose. One queue, one workflow, one button. No knobs you have to learn.

Capture without breaking flow.

Chrome extension or embedded widget. One sentence + the page; console logs, network trace, screenshot, and DOM selector ride along.

ExtensionWidgetDOM + traces

Auto-classify, not just bugs.

Bugs, feature requests, copy changes, chores, questions. Bugmint tags the type, drafts a clean title, and dedupes against open tickets.

5 ticket typesDedup

∆

Routing rules, per trigger.

"P1 bugs to acme/api at capture. Copy changes to #copy on triage. Questions stay in inbox." Admin-defined, previewable, enforced.

GitHubSlackCapture or triage

Hand off to coding agents.

The Bugmint MCP server exposes list / claim / attach_pr / mark_resolved to Claude Code, Cursor, Codex. Devs grab tickets without leaving the editor.

MCPClaude CodeCursor

☞

GitHub App, native.

Routing rules open issues in the right repo with full ticket context. Install once via the GitHub App — no PATs, no per-repo config, scoped to the repos you pick.

GitHub AppPer-repo scope

Audit trail, end to end.

Every capture, classification, routing decision, claim, PR, and merge — logged and exportable. Your compliance team will like it.

Audit logActivity feed

What teams say

Quiet mornings, again.

Bugmint is in early access with a handful of engineering teams. Here's what they've told us.

“

QA stopped writing five-line Slack messages and started filing in Bugmint. By the time I open the inbox, the ticket is already classified and routed.

Maya Rhodes

Staff eng · ledger platform

“

Copy changes used to live in DMs forever. Now they land in #copy with full page context the moment they're triaged.

Dan Sokolov

PM · platform

“

The handoff to Cursor is the real win. List, claim, attach the PR — the ticket lifecycle stays clean without me touching the dashboard.

Priya Anand

Eng mgr · mobile

Pricing

Honest pricing, no surprises.

Start free, upgrade when you feel the value. No seats, no call-us-for-a-quote tiers. Cancel anytime.

Free

$0/ month

For side projects and small teams kicking the tires.

Up to 10 connected repos
Unlimited captures & classification
GitHub App + Slack webhook routing
MCP server for coding agents
Community support

Start free

Team

$49/ repo / month

For teams that want Bugmint as their org-wide intake layer.

Unlimited repos & captures
Per-rule, per-trigger routing
Role-based access & invites
Audit log export
Priority email support

Start 14-day trial

Enterprise

Custom/ annual

For regulated teams that need their lawyers to be happy too.

Everything in Team
Self-hosted or single-tenant
SSO / SAML, SCIM, IP allowlist
Custom DPA, SOC 2, security review
Dedicated slack channel

Talk to founders

Questions, answered

The things buyers actually ask.

Didn't find yours? Email the founders — we answer within a day.

So Bugmint doesn't auto-fix bugs?+

No. Bugmint is the intake layer, not the fixer. Tickets land in your inbox. Engineers handle them in the dashboard, or coding agents (Claude Code, Cursor, Codex) pull them via MCP and open the PR. Bugmint tracks the loop end-to-end but never writes code itself.

Why use Bugmint if I already have Linear / Jira?+

Bugmint is upstream of those tools. Linear is great for the engineering team's planning surface; Bugmint is the front door non-engineers actually use. QA, PMs, and support file in Bugmint — captures with full context — and routing rules deliver the structured ticket to Linear, GitHub, Slack, or your coding agent.

Who installs the extension — engineers or everyone?+

Everyone who notices things. The extension is for the QA on staging, the PM in a demo, the support agent reading a Zendesk ticket. Engineers don't need it — they consume the queue from the dashboard or via MCP in their editor.

What does the GitHub App actually do?+

Opens issues in the repos your routing rules target, with the full ticket body (description, page URL, screenshot, classification). Scope is issues:write on the repos you select during install — nothing else. We don't push code, can't merge PRs, and never touch protected branches. Bidirectional sync (closing the GitHub issue flips the Bugmint ticket to done) is on the near roadmap.

How is captured data handled?+

Console logs, network traces, screenshots, and DOM selectors are stored only on tickets your team can see. We don't train on your data. Enterprise customers can opt into self-hosted or single-tenant deployment so nothing leaves your infrastructure.

What integrations do you support today?+

GitHub App (creates issues on capture or triage). Slack via webhook URLs (notifications on routing). MCP server for any coding agent — Claude Code, Cursor, Codex. Outbound webhooks for everything else. Linear / Jira writeback and Slack OAuth (with interactive Claim buttons) are on the roadmap.

Can I self-host?+

Yes, on the Enterprise plan. Bugmint ships a container that runs in your VPC or Kubernetes cluster, with your own egress rules and model endpoint. Your code, traces, and signals never leave your infrastructure.

How do you charge — per seat or per repo?+

Per repo. Seats are free. We charge for the thing that drives value (repos Bugmint is actively watching), not for headcount — so you can roll it out across the whole org without a procurement conversation about license counts.

What about SOC 2, GDPR, and DPAs?+

SOC 2 Type II is in progress (Q3 2026). GDPR is in place — EU data residency available on Enterprise. Standard DPA is signable online; custom DPAs are available for Enterprise. Ask us for our security brief.

Can I cancel anytime?+

Yes. Team plans are month-to-month with no commitment. Uninstall the GitHub App and billing stops at the end of the current period. Enterprise contracts are typically annual.

Get started

Your intake layer should be invisible.

One sentence in the extension. Structured ticket on the other side. Engineers and agents pick from the same queue.

What's included · free tier

Connected repos10

Captures per monthUnlimited

Ticket typesAll five

MCP serverIncluded

Install time~2m

No card required

SOC 2 · in progress GDPR · ready v1