Skip to content

Faylee records a bug in the browser together with what a developer needs to fix it: what happened on screen, the console, every network request, the steps that led there, and the device it happened on. You share it as one link.

Every Faylee report, whether it is a video, a screenshot or an instant replay, carries the same context from the page:

  • What you saw. A video of the tab or screen, a screenshot, or a replay of the page itself that plays back and can be inspected.
  • Console. Every console message at every level, uncaught errors and unhandled promise rejections, with the stack for warnings and errors.
  • Network. Every request the page made, with its method, URL, status, request and response headers, and the bodies of text requests. WebSocket and EventSource connections come with their messages.
  • Steps. Clicks, typing, form submits, key presses, scrolling and page changes, written out as steps to reproduce.
  • Environment. The browser, the system, the window size, the network speed, when it was captured with the time zone, Web Vitals and memory use.
  • Your app’s context. Anything your app passes to window.faylee.metadata(), such as the signed-in user or the release. See Adding your app’s context.

Secrets are hidden in the browser before anything is uploaded. Authorization headers, cookies, tokens and password fields never leave your machine.

The Chrome extension is where you capture. From its button in the toolbar you take a screenshot, record a tab or your screen, or save an instant replay of what already happened. It also works in Edge, Brave and Arc.

The web app at app.faylee.app is your workspace. It holds every recording, and its viewer plays the video next to the console, network and steps, in step with each other. Your team comments, triages and files issues from there, and an assistant can read the recording and point at the likely cause.

MCP and the CLI hand recordings to coding agents. Paste a Faylee link into Claude Code, Codex or Cursor and the agent reads the report the way a teammate would.

Recording links and the site widget collect reports from people who do not have the extension. A recording link opens a page where a customer or colleague records their screen in the browser, with no account. The widget adds a “Report a bug” button to your own site.