Configuration.
One script tag on your site. Everything else lives in your project settings.
<script src="https://pinthread.dev/embed.js"
data-project="YOUR_PROJECT_KEY" defer></script>Script tag attributes
| Attribute | Value | Behavior |
|---|---|---|
src | https://pinthread.dev/embed.js | Required. Always load the widget from pinthread.dev, so you get fixes without redeploying. |
data-project | YOUR_PROJECT_KEY | Required. Copy it from the project’s Install tab. Public, not a credential. |
data-branch | string | Optional. Keeps separate feedback for one branch, such as preview/navigation. Leave it out to share one feedback stream across deployments. |
data-include-hash | boolean | Optional. Set to true for hash-routed SPAs (such as /#/settings) to track separate comments per hash route. |
data-repo | string | Optional. Associates feedback with a repository to enrich agent prompts. |
defer | — | Recommended. The widget loads after your page is parsed, without blocking it. |
Mask private page content
Put data-pinthread-mask on the page element whose content you want to hide from capture, replay, and screen video. This is a page-element attribute, not a script tag option. Replay hides these regions. Screen video masking is best effort, so other visible secrets may appear.
<div data-pinthread-mask>Private account details</div>Load it only on preview builds
Render the tag only where you want feedback, using the environment check you already have. In Next.js on Vercel:
{process.env.NEXT_PUBLIC_VERCEL_ENV !== 'production' && (
<Script src="https://pinthread.dev/embed.js"
data-project="YOUR_PROJECT_KEY" />
)}Production builds then ship without the tag. Already using comments in the Vercel Toolbar? See pinthread vs Vercel comments.
Control it from your code
The tag exposes window.pinthread immediately, queueing early calls until the widget mounts.
window.pinthread.open(); // Open the sidebar
window.pinthread.close(); // Close it
await window.pinthread.refresh();
window.pinthread.destroy(); // Remove the widgetWhen embedding via the npm package, pass includeHash: true to enable hash-route tracking, or pass an explicit page: () => string callback. Call destroy() before your app removes the page, for example in a single-page app that swaps layouts.
Embedded page content
Pinthread can pin elements inside open shadow roots and same-origin iframes, including nested frames. Anchors save each shadow boundary and the frame path so pins follow the target when it moves.
Closed shadow roots and cross-origin iframe contents are not accessible. Install Pinthread inside a cross-origin page separately if that page needs feedback.
Project settings
Open your project in the dashboard. Each project has these tabs:
- Install: the script tag with your project key, and whether it has loaded on your site.
- Comments: every thread on your site, open and resolved.
- Board: the same threads as cards in four columns: Open, In progress, Needs review and Resolved. Each card shows the page, the first comment, the assignee and the priority. Drag a card to another column, or pick a status on the card. Changes by agents and reviewers show within 15 seconds.
- Analytics: for the last 7 or 30 days, threads per page, new versus resolved threads per day, median time to resolve, and activity per person and agent. Agent and human resolutions are counted apart. The numbers come from stored thread times; nothing extra is tracked on your site.
- Members: invitation links for teammates, and who has access.
- Review links: links that let clients comment without joining the project.
- Agent access: tokens and MCP settings for coding agents.
- Settings: project name, access, approved sites, and deletion.
Who can comment
Projects start with link access: anyone who can open your site can read feedback and join as a guest. Switch to invited Google accounts to keep feedback private. Invitations are tied to an email address, expire after seven days, and work once.
Review links
A review link lets a client comment on your site without joining your project. Open the Review links tab, name the link, and pick how long it works: one day, a week, a month, or three months. You can also open it on one page, add a password, or limit it to Google accounts on one email domain, such as acme.com.
Reviewers open the link and enter their name, or sign in with Google when the link has a domain. They then land on your site as guests. They can comment and reply. They cannot change the project. Revoke a link at any time; it stops working at once. pinthread shows the full link only once, so copy it when you create it.