Installation

There is no required developer setup. Choose the capture path that matches the experience and custody boundary.

Hosted discovery

Use Experiences → Discover public experience for public pages and public complete processes.

Enter an https:// URL.
Name the experience.
Review the discovered checkpoints before activating the scope.
Run the first evaluation from the workspace.

Hosted workers do not receive authenticated customer sessions. Evidence is labelled independent only when the complete hosted custody chain proves it.

Browser recorder

Use the Reshot recorder extension for authenticated and non-developer journeys. The extension records the journey in your real browser and applies its field allowlist and redaction rules before upload.

Install the packaged MV3 extension supplied for your workspace.
Open the target experience and sign in normally.
Start recording, complete the journey, and stop at the final checkpoint.
Review steps and sensitive fields before saving the draft experience.

Authenticated extension evidence is customer-attested. Reshot does not claim that a customer browser session is an independent hosted capture.

CLI and CI runner

Install the CLI only when a developer needs deterministic local execution, repository metadata, or delivery policy.

The public npm latest tag currently resolves to 0.0.1-beta.48. It supports the legacy visual-review lane but not the current checksum-bound accessibility evidence contract. Until the next registry release, local-GA development uses the checked-out package and its locked dependencies:

Terminal

pnpm --dir /absolute/path/to/reshot.dev/applications/reshot-cli install --frozen-lockfile
node /absolute/path/to/reshot.dev/applications/reshot-cli/src/index.js setup

Run the target with a production-like local server, then use the same entry point for record, run, and publish. Do not describe beta.48 output as a signed accessibility evidence record.

Next step

Continue to Quick Start. Add PR checks only after the baseline is calibrated.