# Stop sending developers useless bug reports > Source: > Published: 2026-11-10 18:35:42+00:00 Faylee records the screen, the console, every network request and the steps that led there, and shares it all as one link your team, or your coding agent, can fix from. A real Faylee report. Play it, then open Console and Network.Open in a new tab “It’s broken” is not a bug report The person who found the bug saw everything. The developer gets one sentence, then spends days asking for the rest, and often closes it as can’t reproduce. One link answers all of it Every question from that thread is already in the recording. The developer opens one link and has it fixed the same morning. The usual reportWith Faylee Still happening?Which account?Can you try incognito?Works for meDid you clear the cache?Any steps?DDana · Mon 9:12Checkout’s broken, it just keeps spinningMon 9:40Which browser was it?Mon 14:05Is there an error on screen?Tue 10:31Can you send a screenshot?Wed 11:02F12, then the Console tab…Thu 16:18What did you click before?Closed: can’t reproduceFri 17:30 app.faylee.app/s/k3x9a2 Checkout spins forever after “Place order” Video 1:48 with narration Can you send a screenshot? Steps 9 steps, ending at Place order What did you click before? ConsoleTypeError at submitOrder.ts:14 F12, then the Console tab… Network POST /api/orders → 500Is there an error on screen? Device Chrome 129 · macOS · 1440×900 Which browser was it? Dana recorded it Mon 9:12Fixed 12:10 Time to close 3 hoursUsually 4 days Follow-up messages 0Usually 9 Outcome FixedUsually can’t reproduce Everything a developer needs, in one link One click in the browser keeps the whole session on a single clock. Scrub to any moment and the console, the network and the steps line up with it. Every request, every console error with its stack, and the server error behind it when Sentry is connected. The failing call is highlighted the moment you open the link. NetworkEvery request, with the failing one already open.ConsoleErrors with their full stack, on the same clock.BackendThe server’s error from Sentry, matched by trace. Copy any request as cURL or download the session as HAR. POST https://shop.northwind.dev/api/orders 5001:22.3 TypeError: Cannot read properties of undefined (reading 'id')1:22.4 at submitOrder (src/checkout/submitOrder.ts:14:17)at async onPlaceOrder (src/checkout/CheckoutForm.tsx:52:9)at HTMLButtonElement.handleClick (src/checkout/CheckoutForm.tsx:31:5) 2 events from SentryLook up again ValidationError: coupon_code must be a string app/api/orders.py in create_order POST https://shop.northwind.dev/api/orders1:22.3 Trace 4bf92f35…a8e1northwind-apiView trace in Sentry Coupon lookup skipped: coupon_code is null app/services/coupons.py in apply_coupon POST https://shop.northwind.dev/api/orders1:22.3 Reproduce it without asking Faylee writes the steps as they happen, keeps the last few minutes of every tab, and rebuilds the page itself so you can inspect any element at any moment. StepsEvery click and keystroke, written as it happens.Instant replayThe last few minutes of a tab, saved after the fact.Page replayThe page rebuilt, so you can inspect any element. Instant replay stays on your machine until you share it. Nothing is uploaded in the background. Record a tab or the whole screen and talk through it, or take a screenshot and mark it up. Customers can send a recording from a link without installing anything. Screen recordingRecord a tab or your screen and talk it through. Camera optional.ScreenshotsMark it up. Private fields are blurred for you.Recording linksCustomers record from a link, no extension needed. Narration becomes captions and a transcript, and the assistant drafts the title and the likely cause. …then I click place order and it just keeps spinning. 1:22 / 1:48 Expected The order is placed and the confirmation opens. Actual The button spins. POST /api/orders returns 500. Likely cause An empty coupon is sent as null. CheckoutEmailsam@example.comCard numberTotal$0.00Place orderShould be $92.00 Checkout spins after Place order Northwind asked you to record your screen. Press record and pick the screen, window or tab with the problem. Show what happens, and talk it through if you like. Press stop, check the video, and send it. Record my voice tooStart recording Paste the link into Claude Code. Get a fix back. Faylee’s MCP server hands your coding agent the whole report: the video frame by frame, the console, every request and the steps. It finds the cause in your code, fixes it and tells the reporter. What the person was trying to do, what they said, and the moments that matter, on one timeline. open_recording Sees what they saw It can pull up any moment as a frame, with the clicks, console logs and requests around it. get_moment Reports back It comments on the recording at the moment that broke, and the reporter and your team get notified. add_comment Every report lands where your team works File the issue, ping your team’s channel and match the server error, all from the same report. Linear Jira GitHub GitLab Slack Sentry Zendesk Intercom Azure DevOps ClickUp Asana Trello Notion Linear Jira GitHub GitLab Slack Sentry Zendesk Intercom Azure DevOps ClickUp Asana Trello Notion Zendesk Intercom Azure DevOps ClickUp Asana Trello Notion Linear Jira GitHub GitLab Slack Sentry Zendesk Intercom Azure DevOps ClickUp Asana Trello Notion Linear Jira GitHub GitLab Slack Sentry File the issue Filed as you share, with steps and failing requests in it. Comments sync both ways. Ping the channel New reports post to Slack, and replies in the thread become comments on the recording. Match the server error The server error from Sentry shows up beside the failed request, matched by its trace. Ask a customer Support can send a recording link from a Zendesk or Intercom ticket, nothing to install. Your customers don’t need the extension Add a “Report a bug” button to your site with one script tag. Customers send a screen recording, or the last two minutes of the page, with the console and network. No account, nothing to install, and their reports land with the rest. The extension runs in Chrome and other Chromium browsers. Recording links and the site widget work in any modern desktop browser, with nothing to install. Yes. Free covers up to 2 members and 30 recordings a month, kept for 14 days. Paid plans are priced per workspace with unlimited members: Team is $49 a month for the whole workspace, and every new workspace can try it free for 14 days, no card needed. Is it safe to use on production and with customer data? Tokens, cookies, passwords and card numbers become [redacted] in the browser before upload, and you can add your own headers and fields. Click any part of the page to blur it, or mark it with data-faylee-mask. Password and card fields are always blurred, sites on the never-capture list are not recorded at all, and nothing is uploaded until you share. Can customers or non-technical teammates send reports? Yes. Send them a recording link and they record their screen in the browser without an account or the extension. Or add the “Report a bug” widget to your site with one script tag. On a Zendesk or Intercom ticket, the extension makes a link for that ticket, and the recording comes back as a note on it. How does it work with Claude Code and other coding agents? Faylee runs an MCP server. Connect it once with one command, then paste a Faylee link into Claude Code, Codex, Cursor or OpenCode. The agent reads the report, the console, the requests and any moment of the video, fixes the code and comments back on the recording. Yes, if your site serves its source maps, Faylee resolves stack traces to the original file, line and function, and shows the code around the failing line. Maps behind a login or VPN can’t be fetched yet. There’s a REST API for uploading and reading recordings, signed webhooks for new recordings, comments, issues and finished recording links, oEmbed so pasted links unfurl as players, and a CLI that reads any recording from a terminal.