Posted to #eng-platformThread reply
POST /api/teams/members has returned 500 since deploy a41f2c. TeamService.addMember reads team.settings.open, which the migration in that deploy renamed. Roll back, or guard the read.
New
MP4 recordings that play inline in
Slack+Jira
Report Bugs With The
Report Bugs With The
Evidence Attached, Straight
To Slack In One Click
BugOwl captures the screenshot or recording together with the console errors, failing requests and every click that led there, then files it to your team's Slack channel, a Pagerly incident, Jira, Linear or Asana.
No SDK · No snippet · Evidence buffered from page load
Auth headers never leave the browser
Screen + mic recording
Pagerly AI SRE hand-off
Free Chrome extension
I see every bug 👀
getbugowl.com/k3f9x2
Can't add team members
1 error · 1 failed request
Copy link
File report
Acme Admin
Team members
+ Add team member
Nothing happens
0:08 / 0:14
Console1NetworkActionsInfo
0.1slog[app] booted in 412 ms
0.8swarnTeam.members() is deprecated
3.3sclickbutton "Add team member"
3.4serrorTypeError: Cannot read properties of undefined (reading 'open')at openDialog (app.js:2201:14)at onAddMember (app.js:2240:5)
3.5s500POST /api/teams/members · 611 ms
5.1sclickbutton "Add team member"
Files where your team already works
Slack
Pagerly
Jira
Linear
Asana
Pagerly
Jira
Linear
Asana
Chrome extensionFree, Manifest V3
Private by defaultHeaders redacted in the browser
MP4 recordingsPlay inline in Slack and Jira
AI SRERoot cause in the thread
Watch
BugOwl in under a minute.
From “it’s broken” to a root cause in the Slack thread, without one follow-up question.
See it
What the engineer gets. Right now.
This is the report for the bug in the recording above. Click through what arrives with it, before anyone asks a single question.
Report · Can't add team membersCaptured 0:14 · MP4
+0.1slog[app] booted in 412 ms
+0.8swarnTeam.members() is deprecated, use Team.list()at loadTeam (team.js:88:9)
+3.4serrorTypeError: Cannot read properties of undefined (reading 'open')at openDialog (app.js:2201:14)at onAddMember (app.js:2240:5)at HTMLButtonElement.dispatch (vendor.js:3:41112)
+3.5serrorUnhandled rejection: Request failed with status code 500at addMember (api.js:61:11)
MethodURLStatusTime
GET/api/me20084 ms
GET/api/teams/42200131 ms
GET/static/app.jsasset20012 ms
GET/api/teams/42/members20096 ms
POST/api/teams/members500611 ms
RESPONSE BODY{"error":"Cannot read settings.open of team 42"}
GET/api/notifications?since=172674120020058 ms
0.0sNavigated to
/settings/team1.9sClicked tab "Members"
2.6sTyped 18 characters in
#invite-email3.3sClicked button "Add team member", then the error
5.1sClicked button "Add team member" again
- Page
- https://admin.acme.test/settings/team
- Browser
- Chrome 140
- System
- macOS
- Viewport
- 1440 × 900 at 2x
- Language
- en-GB
- Time zone
- Europe/London
Want to see it on a real page? Install the extension, open the demo page and press ⌥⇧S.
What gets captured
Every clue. Zero back-and-forth.
BugOwl buffers from the moment the page loads, so the evidence is already there when you press the shortcut.
Console errors, with the line that threw
Errors, warnings and unhandled promise rejections with their stack traces, so the report points at the code and not just the symptom.
From:console.errorwindow.onerrorunhandledrejection
Failing requests, and what they returned
Every fetch and XHR with method, status and timing, plus request and response bodies for the ones that failed. Static assets are listed too.
From:fetchXMLHttpRequestResource timing
Every click, in order
A timeline of clicks, navigations and form input, lined up against the console and network so cause and effect sit side by side. Typed text is never recorded, only its length.
From:ClicksNavigationInput length
The page, as they saw it
The visible area, a dragged region, the full page stitched in one pass, or a recording of the tab or your whole screen with your voice over it. Mark it up with arrows, boxes, text and blur.
From:ScreenshotFull pageTab recordingFull screenMicrophone
The browser it happened in
URL, browser and version, operating system, viewport, pixel ratio, language and time zone. Nobody has to ask which browser it was.
From:URLBrowserOSViewport
Pagerly AI SRE
One report. Root cause in the thread.
Tick "Investigate" when you file. Pagerly's AI SRE reads the evidence, checks your team's connected tools and posts what it found under your report.
How it works
Capture. Annotate. File. Investigate.
Four steps, and the evidence handles itself in every one of them.
01
Press ⌥⇧S for the visible area, ⌥⇧A for a region, ⌥⇧R to record the tab or ⌥⇧F for the whole screen.
Capture
02
Arrows, boxes, text and blur on the capture. Trim the recording and say what you expected.
Annotate
03
Pick a Slack channel, an incident, or a Jira, Linear or Asana project. The capture goes along in that tool's format.
File
04
Tick one box and Pagerly's AI SRE picks the report up and replies with a likely root cause.
Investigate
“
Can you send me the console? It is the second message in almost every bug thread. BugOwl sends it with the first.
Every bug threadThe problem BugOwl exists to fix
Get started
Install it, sign in with Pagerly, done.
Two minutes, no setup. Everything your Pagerly organisation already connected is ready to file to.
1. Install BugOwlEarly accessThe Chrome Web Store listing is in review. Until it is live, install BugOwl directly; it takes a minute.
- Download the extension and unzip it
- Open chrome://extensions and turn on Developer mode
- Click Load unpacked and pick the folder
- Pin the owl to your toolbar
2. Sign in with PagerlyOpen BugOwl and sign in with your Pagerly account. Destinations come from your Pagerly org.
- Post to your team's Slack channel
- Declare an incident that pages whoever is on call
- Create Jira, Linear and Asana tickets
- Hand the report to the AI SRE
- Share links anyone can open
Replaces the back-and-forth
One click. Not seven messages.
What it usually takes to turn "it's broken" into a ticket someone can act on.
What the engineer needsUsuallyBugOwl
A screenshot with the problem markedAnnotated, blurred where it mattersSnipping tool, then paste
A recording of the stepsMP4, with your narrationA separate screen recorder
Console errors with stack tracesFrom page load, not from when you noticed"Can you open DevTools?"
The failing request and its responseStatus, timing and bodyA HAR export
Steps to reproduceEvery click, in orderWritten from memory
Browser, OS and viewportCaptured automatically"Which browser was it?"
A ticket in Jira, Linear or AsanaIn that tool's format, capture attachedCopied over by hand
Getting all of it to the right teamSeveral messagesOne click
Who it's for
Four teams. Same report.
For QA
Repro steps write themselves
Every click is already in the report. File straight into the sprint's Jira or Linear project with the recording attached.
For support
From "it's broken" to a real report
Reproduce what the customer saw and post it to the owning team's Slack channel with everything engineering needs.
For product and design
Point at exactly what's off
Mark up the screen, record the flow and drop one link in the thread. The link stays the same when you edit.
For engineering
Start from the stack trace
The error, the request that failed and the click that set it off, before you open DevTools. Or let the AI SRE look first.
Questions?
Answers.
Is it free?
Yes, the extension is free. It signs in with your Pagerly account, and what it can file to comes from what your Pagerly organisation has connected: Slack, incidents, Jira, Linear, Asana and the AI SRE.
What format are recordings?
MP4 with H.264 video and AAC audio on Chrome 126 and later, so they play inline in Slack, Jira and QuickTime. Older versions of Chrome record WebM instead.
Does it upload automatically?
Only when you're signed in and "Instant share link" is on, which it is by default so the link is ready the moment a capture finishes. Turn it off in settings if you'd rather blur things before anything leaves your machine.
What about sensitive data?
Authorization, Cookie and similar headers are redacted before anything leaves the browser. Request and response bodies can be switched off, or dropped for URLs matching patterns you set. Typed text is never recorded, only how many characters went into which field.
Do I need Pagerly?
Yes, BugOwl signs in with Pagerly. That is what gives it your team's Slack channels, incident paging, Jira, Linear and Asana with nothing to set up. If you are new to Pagerly, start free and connect Slack; it takes a few minutes.
Is it on the Chrome Web Store?
It is in review. Until the listing is live, install it directly: download, unzip, load it in chrome://extensions. It takes about a minute. Once the listing is live, install it from the store and remove the direct copy.