Browser capture

Before you beginCopy Anchor Link

Install your app's dependencies, sign in, and select an organization. Use an interactive terminal and a desktop display. Browser tools may download on first use. Use synthetic data suitable for everyone who can access the reproduction.

Browser capture uses the scenario flow. capture browser is an alias for capture scenario.

Connect to a running applicationCopy Anchor Link

Start your app on port 3000 using its normal development command. From the app's source directory:

reprolane capture scenario --port 3000 --route /checkout

Replace the port and route with your local app's values. Reprolane opens the local page and starts a walkthrough. Demonstrate the failure and follow the terminal prompts to finish and select the failure. Connecting to an existing server leaves that server running.

If Reprolane should start your app, provide its actual startup command. For a project that accepts a port flag, from the same directory:

reprolane capture scenario \
  --start "npm run dev -- --port 3000" \
  --port 3000 --route /checkout

Without explicit startup choices, interactive capture asks whether your server is already running. A project without a dev script needs an explicit startup command.

Sign in or record videoCopy Anchor Link

Use --auth when your application needs an interactive sign in. Use --record for a recording, or --walkthrough for interaction without video. Choose one of those modes.

From the app directory, with your server running on port 3000:

reprolane capture scenario --port 3000 --route /checkout --record

Recording and upload are separate. Screenshots and video are excluded by default. If offered, enable review, inspect the exact media, and explicitly approve it. Declined or unreviewed media does not appear in Visual diagnostics.

Inspect the resultCopy Anchor Link

Review source, sanitized diagnostics, media choices, and the organization before uploading. Open the resulting URL and check the available browser evidence.

A local walkthrough may contain useful diagnostics without a complete failure baseline. In that case clean verification can be unavailable. Local app network access also does not grant the sandbox access to external services.

For a specific repeatable assertion, use an authored scenario. If the browser fails to start, see troubleshooting.