A precise handoff from browser to repository

Stop explaining
where it broke.

Point at the failing DOM. Pinhere keeps the page, structure and screenshot so your coding agent can claim, fix and report back.

View workflow
shop.aurora.co / checkout
External page
AURORA GOODS
Your order · 2 items
Field notes$24
Canvas pouch$36
Total$60.00
Payment details
Email
you@example.com
Card information
4242 4242 4242 424212/28
Pay $60.00
01
OPEN
02
IN PROGRESS
03
DONE
Safari 15.4+ · Chrome 116+ · v0.1.13

Point at bugs from your phone or desktop browser

Safari and Chrome share the same secure workflow. Pinhere reads the current page only when you activate the extension, then sends the selected DOM and screenshot to your workspace.

iPhone / iPad first

Safari extension

Touch-first selection: hold to preview and release to choose. Built for iPhone, iPad, and Mac Safari.

TestFlight coming soon
iPhone / iPad · Install with TestFlight

iPhone cannot install a ZIP directly. The beta will be distributed through Apple TestFlight; install it here, then enable Pinhere under Settings → Safari → Extensions.

Desktop browser

Chrome extension

For desktop Chrome, with hover targeting, DOM selection, screenshot cropping, and issue submission.

Download Chrome extension
ZIP · about 100 KB · Chrome 116+
Manual Chrome install01—03
  1. 01

    Download and unzip

    Download the ZIP package and extract it to a folder you can keep.

  2. 02

    Open Extensions

    Enter chrome://extensions in the address bar and turn on Developer mode.

  3. 03

    Load Pinhere

    Choose Load unpacked, then select the folder you just extracted.

From page context to shipped fix01—04
01

Select DOM

02

Structure issue

03

Agent claims

04

Status returns

Give frontend feedback executable context

From “something is wrong here” to agent-ready work

Pinhere is a visual bug reporting tool that connects the live webpage to the code-fixing workflow. It keeps the page URL, selected DOM element, screenshot, and description in one structured issue, cutting the back-and-forth between product, design, QA, and engineering.

01

Select the exact DOM element

Use the Safari or Chrome extension to point at the broken element and preserve its page URL, structure, and reproducible location instead of relying on vague written directions.

02

Keep screenshots in context

Store the interface capture, annotation, and issue description together. Layout defects, copy mistakes, and interaction bugs remain easy to understand when they change hands.

03

Built for AI coding agents

Expose structured issues through a stable API so an AI coding assistant can claim work, update its status, and report the completed fix back to the board.

Who uses Pinhere?

01

Product and design

Point to the exact element during review so every visual comment maps to an implementation target.

02

QA and frontend

Capture reproducible UI bugs without scattering screenshots, URLs, and selectors across separate tools.

03

AI engineering teams

Give coding agents real browser context and close the loop from discovery and claim to fix and status update.

No realtime service, repository binding or black box. Just a stable contract and reproducible defect context.

Pinhere protocol / v1

Visual bug reporting and AI fixes

How is Pinhere different from a screenshot tool?

A screenshot stores pixels. Pinhere also records the selected DOM element, page origin, and structured status, so a developer or AI coding agent can continue the work.

Does it replace project management software?

Pinhere focuses on capturing and handing off webpage UI defects. It provides a lightweight board and stable protocol without forcing repository binding or heavyweight project management into feedback.

Can search engines see private screenshots?

No. Only the public landing pages are indexable. Sign-in, workspace, authorization, and private issue pages are marked noindex and remain protected by account permissions.