Screen & desktop recording — full video of any app
Copy-for-AI — one-click debugging prompt
HAR export & copy-as-cURL
Custom tale titles & notes
Up to 250 stored tales
Council
$18/ month
In-app AI debugging, integrations & guest capture.
Everything in Fellowship, plus:
Debug-with-AI — fix tales in-app with your LLM
Unlimited stored tales
Create Recording Links — guest screen capture, no install
GitHub, Jira & Slack integrations Soon
Priority support
Billed monthly, cancel anytime. Test mode — use card 4242 4242 4242 4242.
Documentation
Set up in a few minutes
Create a Supabase project, run the schema, enable Google sign-in, and drop in your keys. The full walkthrough covers the extension, the website, sharing and privacy.
Yes — sign in with Google so your tales are saved to your library and can be shared. Recording is disabled until you're signed in.
Where are my recordings stored?
In your own Supabase project: capture data and screen videos in storage, lightweight metadata in the database. Tales are private until you share them.
Can it record map or canvas apps?
Yes. Tab mode now captures WebGL/canvas content like MapLibre maps, and screen mode records anything pixel-perfect.
What happens to sensitive data?
Sensitive request headers such as authorization and cookies are partially masked at capture time, and bodies are capped in size.
Ready to tell your first tale?
Sign in and record a bug in under a minute.
Your tales
No tales yet
Record one from the Buggins extension — pick a tab, screenshot, or your screen — and it’ll appear here.
Nothing matches your search
Try a different title or URL.
Current planCompanion
You’re on the free Companion plan.
Test mode — pay with card 4242 4242 4242 4242, any future expiry & CVC. Cancel or switch anytime from Manage billing.
Send a secure link to anyone — a teammate, a client, a tester. They record their screen right in the browser, no install needed, and the recording lands in your tales. Just like sending a Jam.
Create a recording link
Your link is ready — share it:
Your links
No links yet
Create one above and share it — guest recordings will show up in your tales.
Account
—
Integrations Council
Connect an issue tracker, then turn any tale into a ready-to-work issue — repro steps, console errors, failed requests and environment included.
Buggins turns a bug into a tale — a replayable recording with the console, network, and system context a developer needs to fix it without a single “can you reproduce that?” Capture happens in the browser extension; your tales live in this web app where you share them and turn them into issues.
The extension — a Chrome extension that records what's happening in a tab or on your screen, along with console logs, network requests, and system details.
The web app — where every recording (a “tale”) is stored, replayed, shared, and pushed to your issue tracker.
Sign in to both with the same account and your captures appear here automatically. A tale can be a lightweight DOM replay, a screen video, an annotated screenshot, or a guest's screen recording submitted through a link.
Install the Buggins extension from the link in the app sidebar (Get the extension). After it loads, pin it to your toolbar so the icon is always one click away.
2
Sign in
Open the extension popup and sign in. Use the same account on the web app — that link is what makes your recordings show up under Your tales.
3
Reload open tabs
After installing or updating, reload any tabs you want to record. The recorder is injected on page load, so already-open tabs need a refresh before they can be captured.
⚠️
Always reload a tab after updating the extension too. An old, orphaned content script can't talk to the new background worker.
Open the extension on the page where the bug happens. In the Capture tab you'll see your recording options. Pick This tab, watch the short countdown, then reproduce the problem. Hit stop and Buggins saves the tale — replay, console, network and system details included — to your library, with any errors pinned on the timeline.
Open the web app, find the tale under Your tales, and press play. From there you can scrub the replay, inspect logs, share a link, or file an issue.
The extension popup groups capture into two tabs. The Capture tab holds four modes:
This tab All plans
Records a lightweight, fully-inspectable DOM replay of the current tab using rrweb — the actual page structure, not a video. Small to store, and you can hover and inspect elements in the replay. Best for most web-app bugs. Canvas and WebGL (e.g. maps) are captured too.
My screen Fellowship
Records a video of a screen, window, or tab via your browser's screen-share picker. Use it when the bug spans multiple tabs or native UI that a DOM replay can't reach.
Screenshot All plans
Drag to select a region, then annotate it (pen, shapes, blur for sensitive data) and add a description before saving. See Annotated screenshots.
Capture last glitch All plans
Instantly saves the last ~30 seconds that already happened — no need to hit record first. Powered by the always-on instant-replay buffer. Perfect for the bug you only notice after it flashes by.
Every DOM-replay tale bundles far more than a recording. Open one and you'll find:
Replay — scrub the DOM (or video) on a seek bar, play at speed, jump frame to frame.
Console — every log, warning and error, with stack frames, captured in order.
Network — each request with method, URL, status, timing, and payloads.
System — browser, OS, viewport, device-pixel-ratio, locale and timezone, so “works on my machine” ends here.
Errors on the timeline — failures are marked in red and amber right on the seek bar; click to jump to the moment things broke.
Steps — the interactions leading up to the bug, reconstructed as reproduction steps.
Text selection — any text you highlighted during recording replays exactly. See Text-selection replay.
🧭
System details and counts (console errors, failed requests) also appear as chips on each tale card in your library, so you can triage without opening every one.
Buggins keeps a rolling DOM recording of the current tab in the background, holding roughly the last 30 seconds at all times. When you click Capture last glitch, that buffer is saved as a tale — so you can capture a bug that already happened, with its replay, console and network intact.
The buffer is controlled by the Keep instant-replay buffer running toggle in the Capture tab. It's on by default; turn it off on very heavy pages if you'd rather not record DOM in the background.
💡
Leave it on for everyday debugging. The most valuable bug report is often the one you weren't expecting to need.
When you highlight text during a This tab recording, Buggins captures the selection and redraws it in the replay, synced to the timeline — so reviewers see exactly what you pointed at. This is handled with a dedicated overlay so the highlight is always visible on playback, even though the replay runs in a background frame.
🖍️
Selection replay applies to DOM-replay (This tab) tales. Screen and guest recordings are video, where the highlight is already in the pixels.
Choose Screenshot, drag to select an area, and the annotation canvas opens. Draw with the pen, drop shapes to point at things, and use the blur tool to hide sensitive data before anything is stored. Add a short description, then save — it becomes a tale you can share or attach to an issue like any other.
🙈
Use blur on tokens, names or account numbers in the image. Blurring happens before the screenshot is saved.
Tales are private by default. When you're ready to hand one off, create a share link from the tale view — anyone with the link can open the full tale: replay, console, network and system details, no account required. Stop sharing at any time and the link goes dead.
🔗
Filing a GitHub or Jira issue auto-shares the tale so assignees can open the replay from the issue. See GitHub & Jira.
Recording links let anyone capture a bug for you without installing anything. Send a link to a teammate, a client, or a tester; they open it in any modern browser, record their screen, and the recording lands in your tales — like sending a Jam.
Create a link
In the web app, open Recording links in the sidebar (visible on Council), give it a title and optional instructions, and click Create link. Copy the URL and share it. You can also create one straight from the extension's Collect tab.
The guest opens the link, sees your title and instructions, clicks Start recording, picks a tab/window/screen in the browser's own picker, reproduces the bug, optionally taps Mark issue to pin a moment, then Stop & send. It uploads and appears in your tales with a guest chip and the submitter's name.
What it captures
A guest page with no extension can record the guest's screen video and audio, their system info, and the timestamped notes they add.
⚠️
A web page can't read the console or network of a different tab — that's a browser security boundary, not a limitation we can lift. The screen video is the capture. For full console/network telemetry, the reporter needs the extension.
Links can be deactivated anytime from the Recording links view; guests then see that the link is no longer active.
Connect an issue tracker and turn any tale into a ready-to-work issue. Buggins writes a full body — reproduction steps, console errors with stack frames, failed network requests, environment, and a permalink back to the replay — then links the issue to the tale and tracks its open/closed state.
Connect GitHub
Create a fine-grained personal access token (GitHub → Settings → Developer settings → Fine-grained tokens) with Issues: Read and write on the repos you want. In Buggins, go to Settings → Integrations, paste the token and a default owner/repo, and click Connect.
Connect Jira
Create an API token at id.atlassian.com → Security → API tokens. In Buggins, enter your site (https://your-team.atlassian.net), account email, the token, and a default project key (e.g. BUG), then Connect.
🔒
Tokens are stored server-side and write-only — they're never returned to the browser after you save them.
File & track an issue
Open a tale you own and click Create issue, pick the provider and confirm the target. The issue is created with the full body below, and the tale shows a live status badge. Sync status re-checks open/closed from GitHub or Jira anytime.
Captured with Buggins. Replay: https://…/tale.html?share=…
Page: https://app.example.com/checkout
Environment: Chrome 126 · macOS · 1440×900 · en-US
### Steps to reproduce
1. Open cart
2. Click "Pay now"
### Console errors
- TypeError: cannot read 'total' of undefined
at checkout.js:42
### Failed network requests
- POST /api/pay → 500
ℹ️
Integrations use tokens rather than OAuth, so there's no app to register — connect and file issues immediately.
One click copies a compact, structured summary of the tale — environment, console errors, failed requests and steps — formatted to paste straight into any AI assistant or chat. Great for a quick “what's going wrong here?”.
Debug with AI Council
Runs an AI analysis of the tale in-app, using your own LLM key. Buggins sends the request directly to your provider — your key and data never pass through Buggins servers. Configure the key in the extension's Options page.
From a tale's network panel you can export captured traffic as a standard HAR file to open in any network tool, or copy any single request as cURL to replay it in a terminal.
PII redaction scrubs tokens, keys, emails and card numbers before anything is stored.
Private by default — a tale is only reachable once you create a share link.
Your LLM key never touches our servers — Debug-with-AI calls your provider directly.
Issue-tracker tokens are write-only — stored server-side, never returned to the browser.
AI keys, PII-redaction rules and the rolling capture buffer live in the extension's own Options page. Right-click the Buggins toolbar icon and choose Options to change them.
Reload the tab. The recorder is injected on page load, so tabs opened before you installed or updated the extension need a refresh.
“My screen” is locked
Screen/window video recording is a Fellowship feature. Companion includes tab, screenshot and instant capture; upgrade for video.
Text selection doesn't show in an old replay
Selection capture applies to recordings made after the feature shipped. Record a fresh This tab tale, highlight text, stop, and it will replay.
A guest recording has no console/network
Expected — a guest page without the extension can only capture screen video, system info and notes. See Recording links.
Issue creation failed
Check that your GitHub token has Issues: write on that repo, or that your Jira project key and required fields are correct. Buggins surfaces the provider's exact error to help you pinpoint it.
Buggins is built to keep your captures yours. Here's exactly what that means.
PII redaction scrubs tokens, keys, emails & cards before anything is stored.
Private by default — tales stay private until you create a share link.
Your LLM key never touches our servers — it's sent straight to your provider for Debug-with-AI.
Issue-tracker tokens are write-only — stored server-side and never returned to the browser.
AI keys, PII redaction and the rolling capture buffer live in the extension's own Settings. Right-click the Buggins icon in your toolbar and choose Options to change them.