Browser extension

The WebPinch Chrome extension lets you pin issues directly on any website you’re browsing — internal staging, a client’s production site, third-party tools, anywhere. Issues land in the project you’ve connected to.

Install

Two ways to use it

1. Open sidebar

Opens the Chrome side panel — the main way to work. Hit Place Pin, click anywhere on the page, then fill in the feedback form. The panel also lists every pin you’ve placed on the current URL (saved in chrome.storage.local), each with thumbnail, number, title, and submission status (Pending / Submitted).

Title and Description both support voice typing — click the mic and dictate instead of typing. Description keeps listening until you stop it; Title stops on its own after a pause.

Useful for: reviewing what you’ve pinned before submitting in bulk, or coming back to pending pins after closing the page.

2. Bookmarklet / embed

If you can’t (or don’t want to) install the extension, the project’s Sharing settings include:

• A bookmarklet you drag to your bookmarks bar — running it injects the same widget
• An embed snippet (a <script> tag) you can drop into a site’s footer to enable the widget for any visitor

Both use the project guest token, just like the extension.

What happens when you pin

When you click on the page:

1. The widget captures a screenshot of the page (base64).
2. Records your click coordinates as relative pinX / pinY values (so they survive different viewport sizes).
3. Calculates a CSS selector for the element you clicked.
4. Reads navigator for browser, OS, and screen size.
5. Captures the page URL.
6. Optionally lets you highlight text to attach a quoted snippet.
7. Optionally lets you record a screen video to attach.
8. Prompts you for title, description, and (if not signed in) reporter email.

When you submit:

1. The screenshot uploads to S3 via POST /api/upload → returns a URL.
2. The full task payload posts to POST /api/guest/<token> with everything captured.
3. The task lands in the project’s first kanban column (typically Backlog).
4. If the user is signed in (signed-in extension mode is planned but currently the extension uses the guest token), reporterEmail is set; otherwise it’s the email you typed.

Privacy and security notes

• The screenshot is the page as you see it, including any text you have selected, form input values, and authenticated content. Be careful pinning on pages that contain other people’s data.
• The guest token is sent as part of the request URL on every submission. Anyone with the token can submit tasks to that project — treat it as semi-public, not as a credential.
• For programmatic access (read tasks, run audits, list projects), use a personal access token instead. The extension uses the guest token because it doesn’t need to read anything.

Pin persistence

The sidebar tracks pins per URL. State is stored in chrome.storage.local under keys like webpinch_pins_<url>, so you can:

• Drop multiple pins, then submit them in batches
• Close the tab and come back later to find pending pins still listed
• See submitted pins at a glance with the Submitted badge

Clearing your browser storage clears these — submitted pins remain in WebPinch (they’re already in the database), but the local “submitted” markers go away.

Limitations

• Chrome only at the moment. Firefox / Safari are on the roadmap.
• Doesn’t capture network requests or console logs. If you need those, use visual review instead — its devtools panel captures console output, network activity, DOM state, JavaScript errors and storage alongside the pin.
• Doesn’t bypass authentication for sites that require login — for that use the authenticated proxy configured per project.

See also