Support
A clear next step.
Find a quick answer below, or tell us where you got stuck. We’ll help you work through it.
Quick answers
These checks solve common setup and access problems. If they do not help, tell us what you tried in your email.
Open the playground and choose Start playground. You’ll use the actual package on a sample storefront in an isolated temporary project. Feedback and files are stored on our servers, and access ends two hours after creation. Invite one person to try live collaboration. Hide keeps your session; Reset deletes its active content and starts fresh. Use sample content, not sensitive data.
For a real project, send a team invitation to their email address. They must verify it with a one-time code before commenting. The separate website playground supports one-use invitations without email signup, but those temporary identities cannot access customer projects.
Choose Invite one person and share the one-use link with a colleague, or open it in a different browser. Tabs in the same browser profile share one identity. Both people review /playground in the main branch. Try posting a comment, adding a reply or reaction, and resolving a thread while the other person watches. A fresh invitation cancels the previous unused link.
On production, staging and preview hosts, press Ctrl/Cmd + Shift + K and sign in to reveal the widget. Check that the SDK is mounted once in the browser, the project API key is correct, and the current hostname is allowed. In an app with server rendering, use the client-only setup for your framework.
Check the email address and your spam folder. Use the resend action when it becomes available, then enter the newest code. If it still does not arrive, email us with the address and approximate time of the request. Never send us the code itself.
Use the same project key as the deployed site, allow localhost in project settings, and sign in with a team member account. Open the same path and query string. Element comments need a matching element on the local page; markup changes can affect where a pin attaches.
Use the email address the invitation was sent to and verify it with the one-time code. Ask the project owner to check whether the invite is active, expired, or already accepted. After accepting, sign in as a team member instead of reusing the invitation.
Install html2canvas in the host app or configure a custom screenshotProvider. Check that the page permits the images and resources being captured. Password inputs and elements marked for redaction are intentionally excluded by the built-in capture.
Install the optional element-source resolver in your app. File and line information depends on the framework and development metadata; it is not available on every page. CommentKit still includes available comment and element context. Copy that context into your coding agent. The optional comment-kit-mcp 0.1.0 package is also available on npm for authenticated, read-only feedback retrieval; it does not add missing source metadata.
Deleting a project does not free its slot immediately. Pro holds the slot until the current billing period ends. Lifetime holds it for 30 days. The pricing page explains the slot rules before you choose a plan.