Pin it on the page.A teammate fixes it.Sometimes that teammate is AI.
relai is visual collaboration for dev teams: pin anything on your live site with full context in one click, and hand it to whoever executes — John, Dana, or Claude Code.
Your order
Order total
Free returns within 30 days · Secure checkout
capturing element…
>
The problem
“See attached screenshot” is not a handoff.
A cropped PNG in Slack loses the URL, the browser, the console error, the element, and the why. Whoever picks it up spends twenty minutes reconstructing what you saw — then asks you anyway. relai captures all of it the moment you pin.
Size selector overflows on mobile
element screenshot · annotated · 390×844
Enhance with AI
Draft & refine a report, then send it to the thread.
Draft a reportThread
pageacme.shop/checkout
nodediv.coupon-row
enviPhone 14 · Safari · 390×844
logs1 console error captured
Status
Labels
Send to
How it works
Pin → Context → Handoff.
Three steps. Nobody writes a repro, and nobody asks 'which page is this?'
Pin it
Click the relai circle on any page of your live site. Aim, click an element — or drag a region, or grab the viewport. That's the whole capture gesture.
Everything comes with it
relai grabs the screenshot, page URL, the exact DOM element, browser and viewport, console errors, and your note. Type, priority, assignee if you want them. You never write a repro.
Hand it off
Assign a teammate, or send it where work lives — a full-context Asana task, a rich Slack message. The pin stays anchored on the page until it's fixed.
The twist
One of your teammates is AI.
You'd tell David 'fix the coupon field.' Now tell Claude Code — the same way.
you> execute pin #4
relai speaks MCP, so the AI agents your team already uses read pins like teammates: full context, no copy-paste, no prompt-crafting. Say execute pin #4 and the agent gets the screenshot, the exact element, the page, and the console errors — everything it needs to act.
Not a chatbot bolted onto a dashboard. A team member who takes tickets and executes them — because the ticket finally contains everything needed to act.
Built for the team, not just the reporter
The whole loop lives on the page.
Every pin is a thread — anchored to the exact spot on your site. Nobody re-explains anything, because the context never left.
Coupon field overflows on mobile
acme.shop · 2h
Nav dropdown misaligned on tablet
acme.shop · 5h
Promo banner overlaps cookie notice
acme.shop · 1d
Checkout CTA contrast too low
acme.shop · 1d
Cart count lags after item removed
app.acme.com · 2d
Search results missing sale prices
app.acme.com · 2d
Hero image blurry on retina
acme.shop · 4d
Currency rounding wrong on invoices
app.acme.com · 3d
Footer links 404 on /docs
acme.shop · 5d
On-page markers
Open issues visible where they live, for everyone on the team — your designer pins, your dev triages, your PM watches it move to Resolved.
A real board
Group by status, priority, or assignee; drag to update. Comments, @mentions, due dates, and the activity log live on the pin.
Roles
Owners, admins, members, comment-only clients. Permissions that match how dev teams actually work.
Multi-site
Per-site keys for production, staging, and localhost. Pin wherever the bug lives.
Sends where work lives
Full context, delivered anywhere.
The handoff matters, not the platform. One click sends the complete pin — screenshot, links, environment, note.
Size selector overflows on mobile
Page: acme.shop/checkout
Element: div.coupon-row
Env: iPhone 14 · Safari · 390×844
Console errors: 1 captured
screenshot · attached inline
full rich-text task — no copy-paste, nothing lost
Size selector overflows on mobile
screenshot · inline image
posted to #web-fixes the moment the pin was saved
Setup
Pin your first site in two minutes.
The Chrome extension is the whole install. No SDK, no build step.
Sign in and pick your site
relai only ever appears for your team. Visitors never see it.
Pin
Click the circle on any page of your registered sites. Production, staging, or localhost.