Your client points at it. Your AI fixes it. Your client confirms it.

How it works

One piece of feedback, from your client to a confirmed fix

A real run on a sample checkout page. Every picture below is the product itself.

1. 1

   Your client points at the problem

   They press Feedback, tap the broken part of the page and write what is wrong in their own words. DevPin takes the screenshot, lets them circle the problem, and quietly adds the browser, the device and the element they tapped. On a computer they can also record up to 30 seconds of the screen.

   
2. 2

   Your AI coding tool gets a work order

   Connect Claude Code or Cursor to https://devpin.app/mcp with one command and a project token. Ask it to fix the open feedback and it reads each pin like this, with the page, the element, the screenshot and the errors the browser logged. Nothing to install. Your AI runs on your machine with your own keys; DevPin never sees your code.

   claude mcp add --transport http devpin https://devpin.app/mcp \
     --header "Authorization: Bearer devpin_yourtoken"

   id: eeb8735b-9f41-498c-a081-a453a2b3c29b
   page: https://staging.northwind.test/checkout (Checkout | Northwind Supply)
   element: <button#place-order> Place order
   selector: main > aside.summary > button#place-order
   position: click (195, 595); viewport 390x844
   status: open
   reporter: dana@northwind-client.test
   environment: Safari 18, iOS 18, mobile, screen 390x844, pixel ratio 3
   screenshot (link valid for 1 hour, includes the reviewer's drawing): https://…/pin-screenshots/…/homepage-before.png
   feedback: The Place order button sits on top of the total. My customers can't see what they will pay.
   console errors and warnings before the report (1):
     - [warning] Layout shift: aside.summary moved 6px after fonts loaded
   failed network requests: none captured

3. 3

   It fixes it and marks it done

   After the change, your AI marks the pin fixed with a note for you, a link to the preview where the client can see it, and a picture of the fixed page. You can also press Mark fixed yourself, or close the issue in GitHub, Linear or Jira.

   resolve_feedback
     pinId: eeb8735b-9f41-498c-a081-a453a2b3c29b
     note: Checkout.tsx: removed the negative top margin on the
           Place order button so it sits below the total.
     preview_url: https://northwind-git-fix-checkout.vercel.app/checkout
     after_screenshot_url: data:image/png;base64,…
   
   Pin eeb8735b-… is now addressed. Your note is on the pin.
   Asked 1 reviewer(s) to check the fix by email.

4. 4

   Your client confirms it

   Your client gets this email: what they reported, before and after side by side when you add a picture of the fix, and two buttons. Looks fixed closes it. Still broken reopens it with their note and tells you. No account, no password. Your dashboard shows which fixes the client has confirmed.

   

   After they press Looks fixed, in your dashboard:

   
5. 5

   Close the round with a sign-off

   Group a batch of review into a round, such as "Homepage, round 2", with a deadline. DevPin reminds the reviewers who have not looked, shows how many items are fixed and confirmed, asks your client to sign off when everything is done, and gives you a report to send them.