How to · Bug reports

How to record a bug report for developers

Last updated 2026-07-15

Fastest way: record it right here — no install, no signup.

Captures the bug, the DevTools console, your narration, and turns the whole thing into a transcript + shareable link + ask-the-video chat.

Click to start recording

The four steps, with developer-specific notes.

A good bug-report video replaces a 200-message Slack thread. A bad one wastes an hour. Here is the workflow that produces the former.

1

Open the bug in the browser tab you will capture

Reproduce the bug first. Open DevTools (F12 or right-click → Inspect), switch to the Console tab so the developer can see the JS errors as they happen, and put DevTools in a useful position (right-side dock, bottom panel — pick whatever makes the bug visible). The Pullsy recorder will capture the whole tab including the DevTools pane.
2

Open Pullsy in a second tab, click "Start recording", pick the bug tab

Open pullsy.online/record in a separate tab. Click the green "Start recording" button. The system capture dialog appears — pick the Chrome tab where the bug is open. Tab capture is the right choice here: it includes the visual state of the bug, the DevTools console, and the network panel if you have it open. The recording is a faithful capture of what you see.
3

Narrate while reproducing: what you clicked, what you expected, what happened

The "Live AI transcript" checkbox is on by default. Leave it on, and Pullsy transcribes your narration as you go. The transcript becomes the bug report — the developer can read it instead of watching the whole video, or use Pullsy's ask-the-video chat to ask follow-up questions like "show me what happened after the 1:14 mark" and jump straight to that moment.
4

Stop, share the link with the developer

When you are done, click "Stop & save". Give the recording a title that includes the bug ID or a one-line summary ("PROD-1234 — checkout button fails on Safari 17.2"). Pullsy generates a shareable link with the transcript, the AI summary, the chapter markers (Pullsy auto-segments at topic changes, but you can rename them on the share page), and the ask-the-video chat. Paste the link into the Jira ticket, the Linear issue, or the Slack thread. The developer can watch, read the transcript, or ask the video a question — all in one URL.

One honest limitation.

Pullsy's recorder captures a browser tab and a microphone — it does not capture the contents of native desktop apps. If the bug is in a native app (Electron, Slack desktop, VS Code's GUI), the Pullsy tab-share method does not work directly. Workaround: open the app inside a remote-desktop session in a browser tab (or run the app inside Chrome via a wrapper), then capture that tab. For pure web-app bugs, the tab-share method captures everything cleanly including DevTools, the network panel, and any console output.

Frequently asked

Should I include the DevTools console in the recording?

Yes, if it is relevant to the bug. A red error in the console at the moment the bug happens is the most useful thing a developer can see — it tells them which line of code threw, what the network response was, and what the React/Vue state was. The Pullsy recorder captures the whole tab, so anything in DevTools is included. For visual-only bugs (a layout glitch, a misaligned button), DevTools adds noise; close it before recording.

How long should a bug-report recording be?

The best bug reports are 30 seconds to 2 minutes. Long enough to show the reproduction, short enough that the developer watches the whole thing. Pullsy's free tier has no time cap, but a 14-minute rambling recording gets skipped. A good structure: 5 seconds of context (the page you are on, the state you are in), 15–60 seconds of the actual repro (click X, then Y, then see Z), 5 seconds of the expected behavior vs. what happened. Pullsy's auto-chapters will segment the recording for you, so even if you ramble, the developer can skip to the relevant chunk.

Can the developer reply with a video instead of text?

Pullsy is a one-way recorder — the developer cannot record a video reply through Pullsy. But they can: (1) leave a text comment on the share page, with a timestamp attached, so the comment is anchored to a moment in the video; (2) record their own Pullsy video in response and share the link back; (3) react with one of the emoji reactions on the share page. The ask-the-video chat is the most useful: a developer who cannot reproduce the bug locally can ask the video 'what does the network tab show at 1:14?' and get a timestamped answer back.