Omniscio

Bug Report Intake (part 4)

Part 4 of the Bug Report Intake page: the table of decisions you can see when a report does not route, the analytics events intake records, what is deliberately out of scope for the first version, and a map of every file and route behind the feature for readers who have the repository open.

On this page

What it is

This is part 4 of the Bug Report Intake page. It is the reference half: the table of decisions you can see when a report does not route, the analytics events intake records, what is deliberately out of scope for the first version, and a map of every file and route behind the feature for readers who have the repository open.

Where to find it

Nothing in this part is a place you visit — it is the reference behind the panel described on the earlier parts. Keep part 1 open for the Bug Intake sidebar row, part 2 for the Sources tab, and part 3 for what a spawned session receives.

How it behaves

Failure modes — what you'll see

Decision When it fires Tag / row state Session spawn?
routed Email: match + safe + under cap + not in cooldown Routed to <Project Name> yes
unrouted Email: subject parsed but no project has that slug Unrouted bug report no
cooldown Email: same slug fired in last 30s Bug intake — cooldown for <slug> (30s) no
cap Email: project hit bugIntakeDailyCap for the day Bug intake — daily cap reached no
invalid Email: body sanitized to empty Bug intake — empty body no
failed Spawn (DB insert or CLI launch) threw Bug intake failed: <reason> attempted; soft-deleted on launch failure
consolidated (email) Email: the copy of an in-app report whose in-app twin already claimed it Audit — Merged into open issue no — the in-app report's session has it
screen_held In-app, teammate, GitHub or Sentry: the safety screen flagged the report or could not check it Review tab + its own inbox card — Held by safety screen, the reason, Spawn anyway / Dismiss no — only you can start it
unrouted (pending review) Sentry: source's first poll exceeded 5 unresolved issues Review tab — Spawn now / Dismiss no
manually_dismissed Sentry: user clicked Dismiss in Review Audit only no
routed (Sentry) Sentry: autoSpawn on, new issue, dedupe row claimed Audit; session linked yes
(no row) Email: subject didn't match the regex; or Sentry: issue already had a bug_intake_processed row none no

Analytics

Successful routes emit a bug_intake_routed feature event with { decision, reportType } metadata for usage tracking. Duplicate detection adds two more: bug_intake_dedup_hint_emitted (Layer 1 prepended a hint) and bug_intake_self_dedup (Layer 2 archived a confirmed duplicate) — source + ids only, never report text. No PII (sender, body, Sentry payload) is recorded in the analytics table. The full audit trail lives in bug_intake_processed with project FK, slug, decision, reason, source kind (email | sentry | github), external_id, external_url, severity, the dedup signature, and the spawned session_id for forensics.

What's NOT in v1 (Sentry vertical, this PR)

  • GitHub manual-spawn from Review + first-connect-deferral audit rows: GitHub auto-spawn polling now ships (see "GitHub intake" above), but the Review-tab Spawn now button stays Sentry-only (a report the safety screen held is the exception: its Spawn anyway works for every source — see the Bug intake safety screen page), and GitHub's first-connect cap silently defers the overflow (no Review row) instead of recording deferrals the way Sentry does. Label-based report-type inference, issue-comment reply-back, multi-repo single sources, and per-source rate-limit backoff are also out of scope for the GitHub v1.
  • Per-project Sentry filtering (level/environment/release) — every unresolved issue is a candidate
  • Per-source prompt override — you can append your own instructions globally and per project (see "Appended investigation instructions" above), but not per individual Sentry source; the built-in investigation framing/preamble itself is fixed across email + Sentry
  • Domain-wildcard email rules (e.g. *@acme.com) — email intake rules match an exact (sender, slug) pair only; a global approved-senders allow-list + per-(sender, slug) rules (see "Email intake rules" above) already exist, but wildcards do not
  • Web form intake — email + Sentry only
  • Auto-reply to unrouted senders — they appear in the inbox tagged unrouted
  • Multi-org Sentry under one credential — one (project, source) row per project today

The rest of the page is on part 1 (overview, sidebar panel and email), part 2 (Gmail, Sentry and GitHub sources) and part 3 (what a session receives, duplicate collapsing and safety). Related features: inbox alerts for the durable cards intake raises, Agent email for the mail channel, and Repoguard, which shares the same Sentry reading code for its own scanner.

Last verified 2026-10-04