Before you start
You need a Claron account, access to the repository, and permission to create a project in the selected workspace. If someone has already invited you to a project, accept the invitation and open that project instead.
Reviewing a website on your own hosting does not require a Claron build. Follow the browser extension guide for that path.
Sign in and connect a repository
Sign in to Claron
Choose your personal account for your own projects or select the workspace that will own the team's project and billing.
Open Projects and choose New Project
Select the Git provider for your repository.
If the repository is missing, open Settings → Version Control, connect the provider, and grant access to the repository
Return to New Project and refresh the selection.
Choose the repository and branch
For a monorepo, set the app's root directory, then confirm the framework, install command, build command, and output settings. See Projects for the configuration details.
Add the required environment variables before starting the build
Create the project and wait for its first successful build.
Open the preview and report an issue
Open the project and its successful build, then start a review from the project review control.
Choose a solo session to review alone or a collaborative session to work with other reviewers
The person starting the collaborative session is its host.
For collaboration, use the toolbar's invitation control and share the generated invite with the intended reviewer
Guests enter the requested name and email before joining.
Open a page in the preview
Choose Point to mark a location or Element to select a page element. Write what happened, what you expected, and the steps to reproduce it, then submit.
Open Annotations in the project and locate the new report
Confirm its page, build, description, and available evidence. This is the success check for your first review.
Add only the tools you need
Install the frontend SDK for source attribution, enable backend evidence for server requests, use the CLI for local fixes, or connect MCP to read evidence in a supported client. None of these tools is a prerequisite for submitting a basic browser report.
For AI Fix Suggestions, open the annotation's investigation panel. Use Integrations to send reports to your team's issue tracker or notification channel.
If a build fails, read its first actionable error and follow Builds & Previews. If a reviewer cannot join, check the invite and their role in Review Sessions.