Faylee is a bug-reporting tool built around one idea: the person who sees the bug should not have to explain it, and neither should you when you hand it to your coding agent. A Chromium browser extension records your screen, console output, network requests and clicks on a single timeline, then turns the recording into a shareable link. An MCP server lets Claude Code, Cursor, Codex, OpenCode or Claude.ai open that link, step through the recording, inspect the failing requests and comment back on the timeline. The homepage sums it up as "Paste the link into Claude Code. Get a fix back."
It launched on Product Hunt on 30 October 2026, built by Uros Nikolic, with Nina Borkovic on the launch team.
Who it's for
Solo builders shipping web apps with Claude Code, Cursor or Codex, who currently describe bugs to their agent in a paragraph of text and a pasted stack trace.
Small teams where a non-technical co-founder, tester or VA finds the bugs and a developer (or agent) fixes them.
Anyone selling a web product who gets "it doesn't work" emails from customers and wants a recording instead.
If you build native mobile apps or work mainly outside the browser, it is not for you yet.
What it actually does
Records everything on one timeline. You record a tab or your whole screen, with narration if you like, or take an annotated screenshot. The viewer lines up the video with console errors (with stack traces), network requests (exportable as cURL or HAR) and generated reproduction steps.
Instant replay. The extension keeps a rolling buffer of the last few minutes of a tab. When something breaks that you were not recording, you save the last few minutes after the fact. Faylee says nothing is uploaded until you share it, and replay is never kept in incognito windows.
Hands the report to your agent. This is the part that matters. Once the MCP server is connected, you paste a Faylee link into your agent and it can call tools such as open_recording (a briefing plus key moments), get_moment (screen, clicks, console and requests around a timestamp), get_network, get_request (full request and response, including a cURL command) and add_comment (writes a note on the recording at a point in time). There is also an investigate_recording prompt that takes the link plus optional notes.
Here is how a session might go (an illustrative example, not a test we ran). A tester records a checkout that hangs. You paste the link into Claude Code with "investigate this and fix it". The agent opens the recording, finds a 500 on the payment endpoint two seconds before the spinner, pulls the request body, traces it to a missing field in your API handler, patches it, and leaves a comment on the recording saying what it changed. You review the diff. Nobody typed a bug description.
This follows the research we covered showing that coding agents fix more bugs when you paste whole files: agents do better with full context than with your summary of it. Faylee gives the agent the runtime context (what the browser actually did) to go with the code.
Redacts secrets before upload. According to its privacy docs, Faylee strips authorisation and cookie headers, fields with names like "password", "secret" or "token", JWTs, bearer credentials and card numbers in the browser, before anything leaves your machine. These rules cannot be switched off. Password, card and one-time-code fields are masked in the video, and you can mask other elements with a data-faylee-mask attribute or block whole sites from capture.
Files the bug where you work. Reports go to Linear, Jira, GitHub, GitLab, Azure DevOps, ClickUp, Asana, Trello or Notion, and to Slack. There is also a REST API, webhooks and a CLI.
Pricing (as of 31 October 2026)
From Faylee's pricing page:
Plan | Price | What you get |
|---|---|---|
Free | $0 | Up to 3 members (viewers free), 30 recordings a month, 5-minute videos, 14-day retention, Slack, one issue tracker, the MCP server. No AI analysis. |
Team | $12 per member a month billed yearly ($144 a year), or $15 billed monthly | Unlimited members and recordings, 15-minute videos, unlimited history, 100 AI analyses per member a month, all trackers with two-way sync, source-mapped stack traces. 14-day trial, no card. |
Enterprise | Custom, annual contract | Retention policies, DPA, security review, SLA support. |
The line that decides whether you pay: recording links for people without Faylee and the on-site "Report a bug" widget are paid-only, along with Sentry, Zendesk and Intercom. So the free tier covers you finding and fixing your own bugs; the moment customers need to report them, you are on Team. You pay only for members who have joined, and prices exclude tax. Startups, open-source maintainers and non-profits can ask for a discount.
Getting started
Sign up at faylee.app and install the extension in Chrome or another Chromium browser.
Connect your agent. In Claude Code, run
claude mcp add --transport http faylee https://app.faylee.app/mcp, then type/mcp, pickfayleeand sign in through the browser. In Codex, runcodex mcp add faylee --url https://app.faylee.app/mcpthencodex mcp login faylee. For Cursor, use the install link under Settings, Agents in Faylee.On the consent page, check the workspace name and click Allow. The single
mcpscope means the agent can read what you can read, and its comments appear under your name.Add masks before your first real recording: put
data-faylee-maskon anything sensitive the built-in rules will not catch, such as customer names in an admin table.Reproduce a known bug, share the link, and paste it into your agent with a short instruction ("investigate and propose a fix; do not commit").
Check what the agent says against the recording yourself before you merge. The read-back loop applies here too: have the agent state the cause and the evidence before it edits anything.
If you are running headless agents, create a personal token under Settings, Extension and tokens, and pass it as a bearer header instead of the browser sign-in.
Alternatives
Jam. The established one-click bug reporter, and it also offers debugging through MCP. Its pricing page lists a free plan with 30 Jams a month, 5 recording links a month, 5-minute recordings, 5 creator seats and 30 AI summaries, with "Debug Jams via MCP" included. Team is $14 per creator a month billed yearly (as of 31 October 2026). Pick Jam if you want a mature product with a few free customer-facing recording links, which Faylee keeps behind its paywall.
Marker.io. A website feedback widget aimed at agencies and client sites, feeding issues into Jira, Linear, Trello and others. Marker.io's pricing starts at $39 a month billed annually, or $59 monthly (as of 31 October 2026), for 3 team seats with unlimited guest reporters, and a 15-day trial. Its comparison table lists a Marker.io MCP. Pick it if most of your bug reports come from clients reviewing a site rather than from you.
BetterBugs is a third name in this category. Its site would not load for us when we checked, so we have not stated its features or prices here; compare its plans on its own site before you choose it.
Limitations
Chromium only for the extension. Recording links and the widget work in any modern desktop browser, but those are paid.
Tight free limits. Five-minute videos and 14-day retention are fine for your own testing and too short for a bug backlog.
Customer reporting costs money. Jam gives a handful of recording links free; Faylee gives none.
It is brand new. On launch day the Product Hunt page showed no reviews and only the maker's comment. There is no independent track record on reliability or support.
You are still sending session data to a third party. In-browser redaction is a good default, but stack traces, page titles and device details are not redacted, and the privacy page does not say where data is hosted. Ask before you record anything containing customer data.
The agent is only as good as its fix. A complete recording does not stop an agent from patching the symptom. Review diffs as you would without it, and watch the extra tool calls if you are tracking what your coding agent costs.
Verdict
Worth installing if you build with Claude Code or Cursor; the free tier covers your own bug-hunting, pay only when customers need to report bugs.
