# Fairlead

> Fairlead Recorder is a Chrome extension for recording browser tests, reviewing diagnostic evidence, and sharing selected files or submitting evidence through a connected project.

Fairlead Recorder captures browser actions, network traffic, console messages and added images for review. Local capture needs no account; connected projects add configured services.

Recorder capabilities and limits:

- Retention: Capture starts after Start and retains a bounded timeline. See the [recording retention limit](https://fairleadhq.com/docs/recorder/developers/capture-support/#recording-retention). The tester determines the outcome.
- Local evidence: Record, review and download artifacts in the browser without an account.
- Redaction: Selected sensitive keys and structured content are sanitized. Console text, notes, screenshots and unparsed bodies need review; there is no pixel editor.
- Downloads: network.har, console.log, steps.json, playwright.spec.ts, puppeteer.js and added screenshot PNGs in a folder, not a ZIP. Downloads include session.md and notes.md when saved annotations exist.
- Backend correlation: Connected recording sends x-fairlead-reproduction-id and optional issue/request IDs. Capture domain rules do not restrict header injection. Account-free sessions send none.
- Connected projects: Sign in before recording for project rules, Bridge issue submission and Data Plane report storage or enhancement. Local download does not upload a report.
- Reproduction steps: Description offers local action/note insertion, reduced-report deterministic generation, and full-report AI generation. Both generated modes require sign-in and enabled project Data Plane storage.

## Primary interfaces

- [Chrome Extension](https://chromewebstore.google.com/detail/fairlead-recorder/njikgkpcbaaeoeaadbofdpakfkglhmjk): Install Fairlead Recorder from the Chrome Web Store.
- [Product overview](https://fairleadhq.com/index.md): Definition, workflow, privacy behavior, comparison, FAQ, and limitations.
- [Full agent corpus](https://fairleadhq.com/llms-full.txt): Public guides, product information, policies and calculator assumptions in one document.
- [Documentation](https://fairleadhq.com/docs/recorder/): Recording, evidence review, downloads, connected workflows and privacy.
- [Capture support and limits](https://fairleadhq.com/docs/recorder/developers/capture-support/#recording-retention): Recording retention, supported evidence, and capture boundaries.
- [Artifact formats](https://fairleadhq.com/docs/recorder/schema/): Runtime Report, local files and the sample reproduction archive.
- [Sample bundle ZIP](https://fairleadhq.com/downloads/fairlead-recorder-sample-v1.zip): Real reproduction: Blocked tag stays after card leaves the Blocked lane.

## QA guides

- [Add notes to evidence](https://fairleadhq.com/docs/recorder/notes.md): Explain an action, request, console entry, or screenshot where reviewers can find it. Notes are saved as written; export includes saved annotations and pins.
- [Attach execution evidence to a TMS](https://fairleadhq.com/docs/recorder/tms-evidence.md): Use Test case to preserve an ID and result with the report, then attach reviewed evidence and enter the result in the TMS manually.
- [Browser permissions](https://fairleadhq.com/docs/recorder/permissions.md): Understand why Recorder requests access to browser data. Browser policy and protected pages can prevent capture despite broad host permission.
- [Capture accessibility test evidence](https://fairleadhq.com/docs/recorder/accessibility-evidence.md): Choose Test case or Explore, capture keyboard and control evidence, separate manual observations, and preserve a scoped accessibility result.
- [Capture an exploratory discovery](https://fairleadhq.com/docs/recorder/exploratory-testing.md): Use Explore to capture an observation, work backward through linked evidence, save the first discrepancy, and choose the next experiment.
- [Console and browser errors](https://fairleadhq.com/docs/recorder/console.md): Inspect messages, exceptions, and their place in the recorded sequence. A clean console does not prove a passed test; console text needs manual privacy review.
- [Create or update an issue](https://fairleadhq.com/docs/recorder/issue-trackers.md): Use Explore, Test case, or Verify fix to create, update, replace, or add evidence to an issue, then verify independent delivery outcomes.
- [Download session artifacts](https://fairleadhq.com/docs/recorder/bundle-contents.md): Save reviewed browser evidence to your computer. Files depend on available evidence; downloads are a folder, not a ZIP or full viewer export.
- [Downloads and generated tests](https://fairleadhq.com/docs/recorder/troubleshooting-exports.md): Resolve incomplete downloads and scripts that need adaptation. Keep the local session while retrying; files depend on available evidence.
- [Environment and performance evidence](https://fairleadhq.com/docs/recorder/environment-and-performance.md): Read browser context and timing measurements alongside the recorded actions. Selected metrics are not a complete profiler; INP and CLS are not calculated.
- [Execute a test case](https://fairleadhq.com/docs/recorder/test-execution.md): Use Test case, map expected results to evidence, choose Passed, Failed, or Blocked, and complete the manual TMS handoff.
- [How redaction works](https://fairleadhq.com/docs/recorder/redaction-rules.md): Understand automatic sanitization and the content that still needs review. Headers may be partially revealed; screenshots and console and notes need manual inspection.
- [Install and open Recorder](https://fairleadhq.com/docs/recorder/installation.md): Install Fairlead Recorder from the Chrome Web Store, pin it to the toolbar, and open the side panel; includes permissions and automatic updates.
- [Investigate slow or unresponsive behavior](https://fairleadhq.com/docs/recorder/slow-or-unresponsive.md): Choose the workflow mode, trace action-to-request-to-visible timing, preserve the measurement source, and hand off a scoped responsiveness finding.
- [Keyboard shortcuts](https://fairleadhq.com/docs/recorder/shortcuts.md): Use Recorder's contextual keyboard controls in the side panel, in-page toolbar, and session viewer. Recorder has no global start, stop, or screenshot shortcut.
- [Local recording and connected projects](https://fairleadhq.com/docs/recorder/local-and-connected.md): Choose account-free recording for local review and downloads, or a connected project for team capture rules and configured destinations. Sign in before starting a project recording.
- [Navigation, tabs, and frames](https://fairleadhq.com/docs/recorder/navigation-and-frames.md): Understand which pages and embedded content belong to your recording. Eligible new tabs are not all browser tabs; frame and Shadow DOM details can be incomplete.
- [Network requests and responses](https://fairleadhq.com/docs/recorder/network.md): Find a request and inspect its captured details. Bodies may be unavailable or truncated; HTTP status alone does not establish application success.
- [Open a stored session](https://fairleadhq.com/docs/recorder/stored-sessions.md): Review project evidence from Control Plane. Stored review has no local attachment editing or test generation; expired handoffs must be reopened.
- [Open the session viewer](https://fairleadhq.com/docs/recorder/session-viewer.md): Use each viewer as a different angle on one recording, follow linked evidence, and preserve your findings. The viewer is a snapshot; reset clears local evidence; its URL is not shareable.
- [Record a smoke or regression batch](https://fairleadhq.com/docs/recorder/regression-testing.md): Use Test case for each result, maintain an external run index, preserve retries separately, and complete the manual TMS handoff.
- [Record test outcomes](https://fairleadhq.com/docs/recorder/test-outcomes.md): Choose Recorder's supported Test case or Verify fix result after assessing the evidence, and record other scoped outcomes in Description or the external system.
- [Record your first test](https://fairleadhq.com/docs/recorder/quick-start.md): Record a short test without an account, stop within the retained timeline, inspect the evidence, assess the result, and download local artifacts before starting a new recording.
- [Recorded actions and user steps](https://fairleadhq.com/docs/recorder/steps-and-events.md): Inspect individual recorded actions and generate user steps. Both generation modes send the report to the project Data Plane; action associations do not prove causation.
- [Recorder overview](https://fairleadhq.com/docs/recorder/overview.md): A tour of Recorder's Explore, Test case, and Verify fix setup, recording controls, viewer tabs, results, and send destinations.
- [Recorder QA guides](https://fairleadhq.com/docs/recorder.md): QA guides for Recorder test execution, capture, review, results, and evidence handoff, with separate developer documentation.
- [Recording and missing evidence](https://fairleadhq.com/docs/recorder/troubleshooting.md): Find the cause of a failed capture or an incomplete recording. Evicted events and unavailable bodies cannot be recovered from the stopped session.
- [Report a bug from recorded evidence](https://fairleadhq.com/docs/recorder/bug-reporting.md): Use Explore to capture a new or existing issue, investigate the deciding evidence, assemble Description, and verify the tracker handoff.
- [Reproduce a reported bug](https://fairleadhq.com/docs/recorder/bug-reproduction.md): A 12-step reproduction investigation with deeper decision branches: verify targets and misleading labels, compare sent and returned state, pin evidence, explain the outcome, and preserve a developer-ready handoff.
- [Review data before sharing](https://fairleadhq.com/docs/recorder/review-redaction.md): Use the Privacy preview ledger to trace policy rules, your decisions, and unsanitized report content before sharing evidence.
- [Screenshots and attachments](https://fairleadhq.com/docs/recorder/screenshots.md): Capture the visible viewport or an area during recording, then add and manage external images in the local Viewer.
- [Sign in and select a project](https://fairleadhq.com/docs/recorder/projects.md): Load your team's recording rules and configured destinations. Signing in does not convert an existing local recording into a project session.
- [Sign-in, uploads, and issue submission](https://fairleadhq.com/docs/recorder/troubleshooting-connections.md): Resolve account and destination failures without duplicating work. A timeout can leave an issue command outcome unknown; check the tracker before retrying.
- [Start, stop, and reset](https://fairleadhq.com/docs/recorder/recording-lifecycle.md): Control capture and preserve the evidence you need. Capture starts on request and the retained timeline is bounded.
- [Storage and data destinations](https://fairleadhq.com/docs/recorder/privacy.md): Know where local and connected session data goes. Disabling report storage does not disable issue commands or screenshot attachment transfers.
- [Testing workflows](https://fairleadhq.com/docs/recorder/testing-workflows.md): Choose the Recorder session type for a QA job, understand its lookup and result controls, and follow the shared capture-to-handoff routine.
- [Understand capture rules](https://fairleadhq.com/docs/recorder/capture-configuration.md): Understand why scope, payload limits, and redaction rules affect recorded evidence. Project sensitive-key lists replace the local baseline; rule changes do not repair shared evidence.
- [Upload a session and enhance the report](https://fairleadhq.com/docs/recorder/session-upload.md): Use your project's report destination and check independent submission results. Issue success does not prove storage success; disabling report storage also disables enhancement.
- [Verify a fix](https://fairleadhq.com/docs/recorder/fix-verification.md): Use Verify fix, compare original and candidate evidence, choose Fixed or Not fixed, and add evidence without implying an automatic issue transition.
- [What Recorder captures](https://fairleadhq.com/docs/recorder/captured-data.md): Understand the evidence available for a browser test. Viewer and download coverage differ; the retained timeline is bounded.

## Developer guides

- [Adapt a Playwright test](https://fairleadhq.com/docs/recorder/developers/playwright-export.md): Adapt a supplied Playwright file in your test project. Generated actions need assertions, fixtures, and safe test data.
- [Adapt a Puppeteer script](https://fairleadhq.com/docs/recorder/developers/puppeteer-export.md): Adapt recorded actions into a runnable Puppeteer workflow. ES-module setup is required; generated actions are not complete test coverage.
- [Capture support and limits](https://fairleadhq.com/docs/recorder/developers/capture-support.md): Check retained-timeline, session-budget, and artifact boundaries before interpreting a shared bundle.
- [Correlate with backend logs](https://fairleadhq.com/docs/recorder/session-correlation.md): Connect a recorded request to application-side evidence. Account-free sessions do not send correlation headers; recorded IDs alone do not establish server receipt.
- [GraphQL and streaming traffic](https://fairleadhq.com/docs/recorder/developers/graphql-and-streams.md): Inspect application errors and streaming evidence beyond HTTP status. HTTP 200 can contain GraphQL errors; standard downloads omit WebSocket frames.
- [Inspect a shared artifact bundle](https://fairleadhq.com/docs/recorder/developers/artifact-bundle.md): Inspect the files in a downloaded Recorder bundle and choose the evidence relevant to an investigation.
- [Inspect console evidence from a bundle](https://fairleadhq.com/docs/recorder/developers/console-evidence.md): Inspect console.log as supplied text. An absent or clean log does not establish a passed test.
- [Inspect network evidence from a HAR](https://fairleadhq.com/docs/recorder/developers/network-evidence.md): Inspect network.har with a HAR viewer or editor. HTTP status alone does not establish application success.
- [Inspect screenshots from a bundle](https://fairleadhq.com/docs/recorder/developers/image-evidence.md): Inspect screenshot files alongside the action timeline and network evidence. Screenshot pixels are not automatically masked.
- [Prepare evidence for coding agents](https://fairleadhq.com/docs/recorder/developers/agent-handoff.md): Give an agent reviewed evidence and a concrete investigation task. No native Recorder MCP or CLI; provide reviewed files and application context.
- [Read environment and timing artifacts](https://fairleadhq.com/docs/recorder/developers/performance-evidence.md): Use session.md and HAR timing for portable context. Standard bundles do not export every environment or performance panel.
- [Read recorded actions from artifacts](https://fairleadhq.com/docs/recorder/developers/action-evidence.md): Read session.md, steps.json, and generated scripts without relying on Recorder Viewer controls.
- [Recorder for developers](https://fairleadhq.com/docs/recorder/developers.md): Use session summaries, HAR requests, console logs, screenshots, and action exports to trace a reported failure and verify a fix.
- [Replay a Chrome DevTools Recorder flow](https://fairleadhq.com/docs/recorder/developers/devtools-export.md): Import recorded actions as a JSON user flow. Initial navigation does not restore login or data; unsupported actions need adaptation.
- [Report structure and artifact formats](https://fairleadhq.com/docs/recorder/schema.md): Choose the right format before building a parser or integration. The sample ZIP contains local artifacts, not a serialized runtime Report.
- [Reproduce a request from a HAR](https://fairleadhq.com/docs/recorder/developers/reproduce-a-request.md): Reconstruct a reviewed request from network.har in a controlled environment. Replay can modify data and does not reproduce browser state.
- [Review shared artifacts for sensitive data](https://fairleadhq.com/docs/recorder/developers/review-evidence.md): Review the supplied bundle files before sharing them with another person or system.
- [The session identifier](https://fairleadhq.com/docs/recorder/developers/session-identifier.md): Connected Recorder sessions send reproduction and optional issue or request identifiers; backend logging must retain them. Capture domain rules do not restrict header injection.
- [Trace an action to a failure](https://fairleadhq.com/docs/recorder/developers/trace-a-failure.md): Follow recorded actions, requests, and errors while keeping causality explicit. Action associations are timing-based leads rather than proven causes.
- [Turn a recording into a reliable automated test](https://fairleadhq.com/docs/recorder/developers/reliable-automated-tests.md): Add checks and repeatable setup to generated browser actions. Generated actions alone do not establish correct behavior; unsupported actions need adaptation.

## Other documentation

- [Fairlead platform overview](https://fairleadhq.com/docs/index.md): Fairlead connects browser evidence, bug investigation, and unit test generation with team review. Recorder captures evidence, Fix proposes fixes with reproduction tests, and Test adds unit tests. Rebalance, Select, and Replay are in development to help maintain quality as code changes.

## The Fairlead platform

- [Platform overview](https://fairleadhq.com/platform/index.md): Fairlead adds autonomous quality engineering capacity alongside development. Fix investigates bugs and delivers fixes with reproduction tests; Test generates and validates unit tests. Teams set scope and review changes. Product calculators use work-time baselines and explicit assumptions to estimate capacity and cost. Human review remains part of the workflow. Rebalance, Select and Replay are in development.
- [Fairlead Recorder for teams](https://fairleadhq.com/platform/recorder.md): Fairlead Recorder for teams is the Recorder extension signed in to a Fairlead project. The project sets the recording scope, redaction keys and storage policy for every tester. Reports are stored in the project's Data Plane, can be given a generated description, and are filed to Jira, GitHub or Azure DevOps through Bridge. Selected content is sanitized; screenshots, console messages and notes need review.
- [Fairlead Fix](https://fairleadhq.com/platform/products/fix.md): Fairlead Fix: Context and telemetry flow into an agentic engine that finds the root cause and writes both the fix and the reproduction tests, shipped as a PR/MR. Developers shift from firefighting to building.
- [Fairlead Test](https://fairleadhq.com/platform/products/test.md): Fairlead Test: A reliable algorithmic workflow that raises coverage with high-quality unit tests, delivered as pull requests, with zero developer effort. Model-agnostic across leading models, with per-language logic built for each codebase.
- [Fairlead Rebalance](https://fairleadhq.com/platform/products/rebalance.md): Fairlead Rebalance: Push slow, flaky end to end and manual tests down to fast, reliable layers. Analyze coverage and criticality to keep the same coverage with far fewer expensive tests.
- [Fairlead Select](https://fairleadhq.com/platform/products/select.md): Fairlead Select: Shift left: select and run only the tests affected by each code change, directly in CI/CD. Instant per-commit feedback instead of hours-long suites, so bugs are caught in minutes, not days.
- [Fairlead Replay](https://fairleadhq.com/platform/products/replay.md): Fairlead Replay: Record manual sessions during development, replay and verify the bulk automatically so QA focuses only on the failed delta, and harden the critical paths into a durable regression suite.
- [Pricing](https://fairleadhq.com/pricing.md): Fairlead pricing: a flat rate per delivered result, $6 a unit test and $18 a bug fix on pay as you go, $5 or less and $15 or less on a monthly commitment, custom on Enterprise $4 or less a test. A run that delivers nothing is not charged. Access is by waitlist for now; when a place opens, the trial is five runs, with no card charged. Prices in USD; taxes may apply. The Fairlead Recorder is free on your own or with your team, and needs no plan.
- [Get started](https://fairleadhq.com/get-started.md): Getting started with Fairlead: connect a repository and optionally secure connectivity, and results begin. Enterprise engagements run a five phase pilot over roughly six to eight weeks to a go or no-go decision. The connector is outbound only, identity aware, isolated per customer and fully logged.
- [ROI calculator](https://fairleadhq.com/roi/index.md): Both economic models over twelve months, from one set of parameters.

## Optional

- [Human-readable website](https://fairleadhq.com/): Visual product overview.

- [Acceptable Use Policy](https://fairleadhq.com/legal/aup.md): What is and is not permitted when using the Fairlead platform.
- [Cookie Policy](https://fairleadhq.com/legal/cookies.md): How the Fairlead platform uses cookies and similar technologies.
- [Data Processing Agreement](https://fairleadhq.com/legal/dpa.md): Terms for processing personal data on behalf of Fairlead platform customers.
- [Privacy Policy](https://fairleadhq.com/legal/privacy.md): How Allyx handles personal data on the Fairlead platform.
- [Subprocessors](https://fairleadhq.com/legal/subprocessors.md): The third parties authorized to process customer personal data for the Fairlead platform.
- [Terms of Service](https://fairleadhq.com/legal/terms.md): Terms that govern use of the Fairlead platform.
- [Fairlead Recorder Extension Privacy Policy](https://fairleadhq.com/privacy.md): When you use Recorder without signing in, nothing is sent to Fairlead. Learn what stays on your device and what to review before sharing exports.