Slack rant + guesswork
- "It’s broken on mobile lol" — no route, no device, no clue
- No console, no network ring, no repro path
- Engineer DMs the tester three times asking what they clicked
- Agent: "I need more information about the error."
When a tester flags something — a bug, a broken layout, the wrong copy — Brevwick turns it into a clean, agent-actionable issue in your tracker. Route, console, network, and device context ride along automatically.
/checkout/payment on iOS SafariExpected: Validation error shown inline.
Actual: White screen; cart.total is undefined at PaymentPage.tsx:142.
Sentry and LogRocket watch your app from the inside and tell engineers what broke. Brevwick is the front door for the bugs a humanfinds — it hands your tracker, and your coding agent, a clean issue with the route, console, network, and device already attached. No “it’s broken on mobile lol.”
PaymentPage.tsx:142 and open a PR.”Four capabilities, one pipeline — from the moment a human tester flags a bug to a tracker-ready issue your agents can action. No re-write step in between.
The widget grabs route, console breadcrumbs, network ring, and device metadata alongside the tester’s note.
A PII-sanitised formatter turns raw notes into tracker-ready Markdown — title, repro, expected, actual.
Reviewers approve, edit, or reject in a keyboard-driven dashboard built for speed.
Approved issues appear in GitHub, Linear, or Jira; Slack notifies your team in the right channel.
Connect once. Brevwick handles the rest — labels, priorities, channels, and cascading project pickers stay in lockstep with your team’s conventions.
Three steps from a human tester’s click to a tracker-ready issue. No manual re-write, no half-formed tickets.
The widget grabs the route, console breadcrumbs, network ring, and device metadata at the moment the bug was seen. The tester just types what they saw.
A PII-sanitised formatter rewrites the note into a tracker-clean Markdown body — title, repro steps, expected, actual.
A reviewer approves, edits, or rejects in the keyboard-driven dashboard. Approved issues appear in GitHub, Linear, or Jira; Slack notifies the right channel.
Drop it in. Set your project key. The widget shows up, context capture starts, and your dashboard lights up the first time someone files a bug.
// 1. Install
$ npm install @tatlacas/brevwick-sdk
// 2. Mount the widget
import { createBrevwick } from '@tatlacas/brevwick-sdk';
const bw = createBrevwick({
projectKey: 'pk_live_…',
});
bw.install();Add the widget. Connect your tracker. Watch the next bug report show up triaged, formatted, and ready for a PR.