Frequently Asked Questions
Use these answers to find the next check or setup step. For version-dependent tooling, also check the installed SDK/CLI version and the detailed guide.
Yes. One-time reviewers can join through a collaborative-session or review-round invitation and report or discuss issues in the invited review context.
Guests cannot read internal staff comments, delete reports, or authorize MCP. Public reports are not visible only to their author. See Team & Roles, Review Sessions, and Review Rounds.
Open the build's logs and find the first actionable error. Check the install command/dependencies, monorepo root, build/output settings, and required variables separately. Fix the cause and retry; see Build troubleshooting.
Connect repository access in Settings → Version Control, not a project Version Control tab. For element attribution, check the supported frontend plugin in the exact deployed build. Source-map uploads are not automatic from the current Vite/webpack plugin setup. See Frontend SDK.
Check the staff role, owning account's credits/plan, repository access, report evidence, and current investigation state. Retry the investigation with its retry action; reopening an issue is separate. See AI Fix Suggestions.
Both solo and collaborative sessions expire after 24 hours of inactivity. A collaborative room is not permanently active until the host ends it. Review-session invites default to seven days and can expire or be revoked. See Review Sessions.
Permitted project staff can move a report to Trash. Clients/guests cannot delete a report even if they created it. Restore it from Trash within 30 days; permanent deletion is owner-only. See Managing Annotations.
No. Enable the required capture permission/SDK before a new session and reproduce the issue again. Missing, locked, incomplete, and expired evidence have different causes. See Replays and Backend Evidence.
Use MCP to read existing evidence from a supported client, Webhooks for event deliveries, Integrations for provider-specific tickets/notifications, and the CLI for local developer actions. Their credentials and permissions are different.
Yes. Connect the Git provider in Settings → Version Control and grant access to the repository. Select that connected repository when creating the project.
Install the CLI, authenticate, and link the correct repository checkout. Supported dashboard actions can then open the local developer workflow through claron://.