PatchReply

Point out changes. Keep everyone on the same page.

Leave voice or typed Notes directly on websites and web apps. Capture screenshots, suggest text changes, and send a clear Review report to your team or coding agent.

Try the Review Lab Try the example below

Free in Chrome. Team is $99 a month billed annually, with a 14-day trial and no credit card.

Try it on an example site

Hold Option or Alt and click anything to add a Note. Click a marker to open one. Select text to suggest an edit. On a touchscreen, tap Add note.

Example site and Notes. They stay on this page and reset when you reload. Voice is optional. Turn it on and each voice clip you save is sent to PatchReply to become text.

Review feedback falls apart between the page and the fix.

Clients, designers, QA, and developers all look at the same build and describe it in different places. By the time a change reaches the person making it, the context is gone. PatchReply keeps each Note on the page it's about, with the evidence attached.

How review feedback arrives today compared with a PatchReply Note
What arrives todayWhat arrives as a Note
A screenshot in Slack with a red circle and "this?" A marker on the Pay button, with the screenshot, the page URL, and the browser it failed in.
An email with 22 bullet points mixing copy, bugs, and taste. A Text edit with the Original and the Replacement, pinned to the headline it changes.
A PDF of the homepage from two builds ago. A Note on the live preview build, with the viewport and device it was left on.
A call where the real decision happens at minute 38. A thread on the Note, an assignee, and a resolution everyone can see.

Capture a Note where the problem is

A Note carries what a reviewer saw, not just what they typed. One Review can cover a whole flow, and Notes stay grouped by page.

  1. Start from the handle

    The review handle sits at the edge of the page. Drag it out of your way. It keeps count of your Notes as you move between pages.

  2. Hold Option and press what you mean

    Press an element, drag across an area, or select text. Alt or Option is the default capture key and you can change it. Without the key the page works normally, so you can click through a flow while you review. On a touchscreen, tap Add note.

  3. Talk, type, or rewrite the copy

    Voice is optional and typing always works. For copy changes, write a Text edit and PatchReply keeps the Original next to your Replacement.

Example Note

Example Note

Voice Note 0:07

Switching to Annual still shows the monthly price on both plans. Studio should drop to forty-seven.
Location data
Clicked an element · .plan--studio .price · 612,418px
Page
staging.tidewell.example/pricing
Environment
Chrome 141 on macOS 26 · desktop · 1440×900 · light

Share one link. Settle every change.

Share a review link with clients and teammates. Discuss Notes, assign changes, track resolutions, and approve the next round, all in one place.

Clients review without an account

Send guests a review link. They open the site, leave Notes, and reply to yours without creating a PatchReply account. Your team decides who holds the link, when it expires, and when to revoke it.

A review link doesn't get anyone past your site's own login, VPN, or preview password. Guests need the same access they'd need to see the page.

Discuss, assign, resolve

Every Note has a thread. Mention a teammate, attach a file, set a priority and labels, and assign the change. Mark a Note or a reply internal and guests never see it.

Shared search and filters find every open Note assigned to you across projects.

Annual toggle doesn't change the Studio price

High
  1. PS

    Priya Shah QA

    Switching to Annual still shows the monthly price on both plans.

  2. DO

    Dana Ortiz Guest

    Good catch. Annual is the plan we're pushing at launch.

  3. JL

    Jordan Lee Developer Internal

    The toggle state never reaches the plan cards. @Sam want the $47 shown with the strike-through?

Assigned to Jordan Lee PricingBug Open

Rounds that end in a clear yes

When the fixes land, send the next round. Guests re-review what changed, then request changes or approve. The whole history stays in a hosted Review report you can open on any device.

Notifications tell each person when a Note is assigned, answered, resolved, or ready to re-review.

Review history

  1. Round 3 2 Notes, 2 resolved Approved by Dana Ortiz
  2. Round 2 6 Notes, 6 resolved Changes requested
  3. Round 1 14 Notes, 14 resolved Changes requested

Review report 22 Notes across 5 pages, 3 rounds

Hand off to the tools you already use

PatchReply isn't another task board. Send a Note to GitHub, Linear, Jira, or ClickUp with its screenshot and location data attached, and status and comments sync back where the tool supports it. Coding agents can read the same Review through MCP or a copied Agent prompt.

tidewell/web · Issue #1184

Annual toggle doesn't change the Studio price

bugpricingAssignee jordanlee

From PatchReply Note 2 on staging.tidewell.example/pricing, round 1.

Switching to Annual still shows the monthly price on both plans. Studio should drop to forty-seven.

Clicked an element · .plan--studio .price · Chrome 141 on macOS 26 · 1440×900

Context screenshot attached

Closing the issue resolves the Note. Comments sync both ways.

Web · TID-214

Annual toggle doesn't change the Studio price

TodoHighAssignee Jordan LeeCycle Launch week

Linked to PatchReply Note 2 with the context screenshot, location data, and environment details.

Switching to Annual still shows the monthly price on both plans. Studio should drop to forty-seven.

Moving TID-214 to Done resolves the Note in PatchReply.

TIDE · Bug · TIDE-88

Annual toggle doesn't change the Studio price

To DoPriority HighAssignee Jordan LeeLabel launch-qa

Environment and steps come from the Note, so the bug report arrives with the browser, viewport, and page it was found on.

Chrome 141 on macOS 26 · desktop · 1440×900 · staging.tidewell.example/pricing

Status and comments sync where your Jira project allows it.

Tidewell · Launch QA list

Annual toggle doesn't change the Studio price

In reviewAssignee Jordan LeeDue Oct 16

The task links back to the Note, so the client's thread stays in PatchReply while the work is tracked in ClickUp.

Closing the task resolves the Note.

Agent prompt · open Notes from the example review 
# Notes from a browser review

A reviewer went through the running app in a browser and left the notes below. Please address each note.

The location data records where the reviewer clicked, dragged, or selected text. Start there when locating the subject, but treat it as spatial context, not exact scope.

## Page: Pricing | Tidewell

URL: https://staging.tidewell.example/pricing

### Note 2: $59/mo

Note:

> Switching to Annual still shows the monthly price on both plans. Studio should drop to forty-seven.

Location data:

- Gesture: Clicked an element
- Selector: `.plan--studio .price`
- Viewport at capture: 1440×900
- Environment: Chrome 141 on macOS 26; desktop; light appearance
Illustrative agent session

YouFix the open Notes in the Tidewell spring launch review.

AgentReading the Review from PatchReply through MCP. 4 open Notes on 3 pages, with screenshots and location data. Starting with Note 2 on the pricing page, where the Annual toggle isn't passed to the plan cards.

AgentInternal Notes stay with your team. Guests' Notes arrive with their replies, so the agent sees the latest decision, not just the first message.

For the pages you review before launch

Deliberate reviews, QA passes, UAT, and client sign-off on browser-based work. Reviewers work inside the browser session they already have.

  • tidewell.example

    Live sites. Review the production site before a redesign or after a release.

  • staging.tidewell.example

    Staging. Review behind your staging login. Your site's access rules stay exactly as they are.

  • pr-482.preview.tidewell.example

    Preview deployments. Each Note keeps the exact URL it was left on, so preview 482 never gets mixed up with production.

  • app.tidewell.example/schedule

    Signed-in web apps. Review dashboards, settings, and states that only exist after sign-in.

  • localhost:5173

    Local development. Review your own build before anyone else sees it.

PatchReply is for invited reviewers. It doesn't add a public feedback widget for your site's visitors, run surveys, record sessions, or capture native desktop and mobile apps.

Free to review. Team when you share.

Capture, local reports, Agent prompts, and exports stay free. Team adds hosting, guests, collaboration, and connected workflows.

Billing period

Free

$0

Chrome extension, forever

Review in Chrome for free. Keep your Notes together across pages and export a Review report or Agent prompt.

Try the Review Lab
  • Movable review handle on the page
  • Typed Notes, Text edits, and voice with your own transcription key
  • Screenshots, location data, and environment details
  • Multi-page Reviews with local recovery
  • Review report PDF, versioned JSON, and Agent prompt

Hosted transcription, cloud history, guests, and collaboration are part of Team.

Team

$99/month

Billed annually at $1,188. Or $119 billed monthly.

Share a review link with clients and teammates. Discuss Notes, assign changes, track resolutions, and approve the next round, all in one place.

See how Team works

14-day free trial. No credit card.

25 internal seats. Unlimited guest reviewers, projects, Notes, and Text edits.

Everything in Free, plus

  • No-login guest review links with expiry and revocation
  • Replies, mentions, attachments, and internal Notes
  • Assignments, priorities, labels, and resolution states
  • Review rounds, re-review, and approval
  • Hosted Review reports and history on any device
  • Hosted voice transcription with a published monthly allowance
  • GitHub, Linear, Jira, and ClickUp handoff, plus MCP
  • Notifications, shared search, and workspace branding
  • Workspace export and permanent deletion

Hosted transcription, storage, and attachments have published allowances. Guests never need a seat.

Questions

Can clients review a staging site that's behind a login?

Yes, as long as they can reach it. A review link gives guests access to the Review, not to your site. If staging needs a password, a VPN, or a sign-in, share that access the way you do today. PatchReply captures inside the browser session the reviewer already has.

Do guests have to install the Chrome extension?

Guests never need a PatchReply account. In Chrome they can use the extension. For guests on other browsers or phones, add the PatchReply snippet to your staging or preview build and they review from the page itself. Your team reviews with the extension.

Does it work on preview deployments and localhost?

Yes. The extension runs on the pages Chrome lets extensions open for you, including preview URLs and localhost. Each Note records the exact URL, viewport, and browser, so a Note from one preview never gets confused with another build.

Do I need a microphone?

No. Typed Notes and Text edits always work. On Free, voice uses a transcription key you provide. Team includes hosted transcription with a published monthly allowance.

Do we need an AI coding agent?

No. Most teams work from the Review report or send Notes to their tracker. If you use Claude Code, Codex, Cursor, or another agent, the Agent prompt and MCP access give it each Note with its location data attached.

Does PatchReply replace Jira, Linear, or our task board?

No. PatchReply holds the review conversation. Tracked work goes to GitHub, Linear, Jira, or ClickUp, and status and comments sync back where those tools allow it.

Who needs a seat?

Anyone on your team who runs reviews, triages Notes, or makes the fixes. Team includes 25 internal seats. Clients and other guests you invite by link don't use a seat.

What happens to our data?

On Free, Reviews stay on your device and exports are your own files. Team stores Reviews in your workspace, and you can export the workspace or delete it permanently.

Can visitors to our live site send feedback with it?

No. PatchReply is for invited reviewers doing a deliberate review. It has no public feedback widget, surveys, or session replay, and it doesn't capture native desktop or mobile apps.

Start the next round on the page.

Try the Review Lab Try the example