Every bug report,
ready to fix

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.

Start for free See a real report

app.faylee.app/s/k3x9a2

Checkout spins forever after “Place order” 1 failed request 2 errors Chrome 129 · macOS · 1440×900

NorthwindCart (2)

Checkout

Emaildana@acme.io

Card4242 4242 4242 4242

Coupon

Placing order…

Linen shirt$68.00

Canvas tote$24.00

Total$92.00

“I click place order and it just keeps spinning.”

Info Console 2 Network 1 Actions

200GET/api/cart0:31

200GET/api/shipping/rates0:48

204POST/events1:02

500POST/api/orders1:22

200GET/api/orders/status1:23

200GET/api/orders/status1:25

500POSTfetch cURL

https://shop.northwind.dev/api/orders

HeadersPayloadResponse

{
  "error": "coupon_code must be a string",  "request_id": "req_8f2c41"
}

1:22 / 1:48

“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.

Still happening?Which account?Can you try incognito?Works for meDid you clear the cache?Any steps? D Dana · Mon 9:12Checkout’s broken, it just keeps spinning Mon 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?~~
Console TypeError at submitOrder.ts:14 ~~F12, then the Console tab…~~
Network POST /api/orders → 500 ~~Is there an error on screen?~~
Device Chrome 129 · macOS · 1440×900 ~~Which browser was it?~~

Dana recorded it Mon 9:12 Fixed 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.

See exactly what broke

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.

Copy any request as cURL or download the session as HAR.

How the viewer works

AllFetch/XHRWS/SSEJSCSSErrors onlyHAR

#StatusMethodNameDurationWaterfallTime

24200GET/api/cart84 ms0:31.2

31200GET/api/shipping/rates212 ms0:48.6

47500POST/api/orders1.9 s1:22.4

500POSTfetchcURL

https://shop.northwind.dev/api/orders

HeadersPayloadResponse

{"error":"coupon_code must be a string"}

AllErrorsWarningsNetwork errors

Coupon field empty, sending default1:21.6

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.

Instant replay stays on your machine until you share it. Nothing is uploaded in the background.

About instant replay

6 steps to reproducePlaywrightCopy

1Click "Checkout"0:04.2<a href="/checkout">
2Click the "Email" field0:29.1<input type="email" name="email">
3Type "sam@example.com" into the "Email" field0:31.6<input type="email" name="email">
4Click "Standard shipping"0:55.0<input type="radio" name="shipping">
5Type into the "Card number" field hidden1:08.4<input name="card-number">
6Click "Place order"1:22.3<button type="submit">

Something broke a minute ago. It’s already recorded.

−2:00−1:00now

Instant replaySave the last 2 minutes AltShiftI

VideoPagenorthwind.shop/checkout

<button class="checkout__submit" disabled aria-busy="true">

Capture it the way it happened

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.

Narration becomes captions and a transcript, and the assistant drafts the title and the likely cause.

Recording a bug

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.

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.

~/northwind — claude

> checkout is broken, see app.faylee.app/s/k3x9a2

⏺ faylee - open_recording (MCP)(recording: "k3x9a2")

⎿ “Checkout spins forever after Place order” · 1:48 · 1 failed request, 2 errors

⏺ faylee - get_request (MCP)(recording: "k3x9a2", id: "14")

⎿ POST /api/orders → 500 {"error":"coupon_code must be a string"}

⏺ faylee - get_moment (MCP)(recording: "k3x9a2", at: "1:22")

⎿ Clicked “Place order” · coupon field empty · said “it just keeps spinning”

⏺ The coupon field was empty, so the order sent coupon_code: null and the server rejected it.

⏺ Update(src/checkout/submitOrder.ts)

⎿ Updated src/checkout/submitOrder.ts with 1 addition and 1 removal

40 items: cart.items,

41 - coupon_code: form.coupon,

41 + coupon_code: form.coupon || undefined,

42 total: cart.total,

⏺ faylee - add_comment (MCP)(recording: "k3x9a2", at: "1:22")

⎿ Posted: “Fixed in submitOrder.ts. An empty coupon was sent as null.”

claude mcp add --transport http faylee https://app.faylee.app/mcp

Works with

Claude Code
Codex
Cursor
OpenCode
Claude.ai

Setup for other agents

Starts from the whole story

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

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.

Add the widget to your site

index.html

<script
  src="https://app.faylee.app/widget.js"
  data-site="site_3kf9…"
  async
></script>

Captures the bug, not the secrets

A report that records the network also records what’s in it.
Faylee hides what’s private in the browser, before anything is uploaded.

Secrets stay in the browser

Tokens, cookies, passwords and card numbers become [redacted] before upload.
Nothing leaves until you share

Recordings wait on your machine until you send them. Trim, blur or leave out the console first.
Blur any part of the page

Click anything private and it stays blurred on that site, or mark it with data-faylee-mask.
Sites Faylee never captures

List the sites to leave alone, like your bank, for yourself or for the whole workspace.

Your own storage bucket, SAML single sign-on, SCIM and an audit log. How Faylee handles your data

Questions, answered

Anything else is in the docs, or write to us.

Read the docs hello@faylee.app

Which browsers does Faylee work in?

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.

Is there a free plan?

Yes. Free covers up to 3 members and 30 recordings a month, kept for 14 days. Team is $15 per member who records per month, and every new workspace can try it free for 14 days, no card needed. Viewers are free on every plan.

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.

Can it read minified stack traces?

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.

Can we keep recordings in our own storage?

Yes. A workspace can store recordings in its own S3-compatible bucket (S3, R2, B2 or MinIO) and set them to be deleted after 30, 90, 180 or 365 days.

Is there an API?

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.

The next bug report
could be the easy one

Add the extension, record a bug, send the link. Your team or your coding agent takes it from there.

Start for free See pricing

Free for up to 3 members14-day Team trial, no card needed

Every bug report,ready to fix

“It’s broken” is not a bug report

Everything a developer needs,in one link

See exactly what broke

Reproduce it without asking

Capture it the way it happened

Paste the link into Claude Code.Get a fix back.

Starts from the whole story

Sees what they saw

Reports back

Every report lands where your team works

File the issue

Ping the channel

Match the server error

Ask a customer

Your customers don’t need the extension

Captures the bug, not the secrets

Secrets stay in the browser

Nothing leaves until you share

Blur any part of the page

Sites Faylee never captures