Public betaBuilt for studios shipping client sites

Client feedback that ships itself

Client comments on your live site come back as pull requests, written by your own coding agent. No Slack threads, no relaying, no back-and-forth.

See how it works

Works on any live site · Your clients don't need an account

The problem

Six tabs of feedback. One prompt box. You’re the glue

Slack, email, Loom, screenshots. You gather every scrap and paste it into your coding agent yourself. One prompt at a time.

RE: RE: RE: Website feedback v29:14 AM
Can we make the hero pop more? Feels a bit flat. Also not sure on the blue tbh.
Tom · #website45m
navbar feels heavy on mobile 😅 can it shrink on scroll?
Maya1h
2:47
Priya left a comment2h
@0:42 this pricing section feels cramped, give it some air?
Sam commented3h
“Sign up” should say “Get started” everywherehomepage-copy.docx
Project notes5h
can we tighten the spacing between sections on mobile? feels too airy

How can I help you today?

Opus 4.8
How it works

The shortest path from “can we change this?” to merged

The client pins what they want, Patch writes the fix, and you decide if it ships.

  1. Hero · headline
    MA
    Mayanow

    Your client

    Pins on your live site and says what to change.

  2. Make the headline bolder#128
    Openpatch wants to merge into main
    1 commit · 2 files changed+24−6

    Patch

    Reads the comment, writes the code, opens a PR.

  3. All checks have passed
    No conflicts with main
    Merge pull request

    You

    Review the pull request and merge.

Features

Everything between the comment and the commit

Pin on the real site, on any screen, with the agent you already use.

yourclient.com
Home · hero
MA
Mayanow

Pin on the real thing

Figma-style comments on any live URL. Your actual site, not a staging mock.

Claude CodeConnect
CodexConnect
CursorConnect

Bring your own agent

Patch drives Claude Code, Codex, or Cursor on your own account. You pick the agent, you keep the keys.

Annotate every viewport

Clients pin on mobile, tablet, and desktop. Every comment knows the screen it came from.

app/layout.tsx
1
2 
1export default function RootLayout({ children }) {
2 return (
3 <body>
4 {children}
5
5 </body>
6 );
7}

Drop in with one component

Install the widget and add one component to your app. Done.

Security

An agent in your repo. On a leash

All the speed of an autonomous agent, with the control a real codebase needs.

Pull requests only

Changes land as PRs on their own branch. Nothing ships until you merge.

Your agent, your keys

Runs on your own Claude, Codex, or Cursor account, with the config you already use.

Access that expires

Per-run repo tokens, scoped to the one repo you linked, revoked after use.

Nothing left behind

Each run gets a fresh, isolated sandbox in the cloud, destroyed when it ends.

patch · run 2c4f1a
Pricing

Simple pricing. Clients are always free

One plan per workspace, sized by projects, runs, and seats. Upgrade when the client work does.

Free

For trying Patch on a single project.

$0/month

Free includes:

  • 1 active project
  • 5 Patch runs / month
  • 1 internal member
  • Unlimited client commenters
  • Bring your own agent key

Studio

Most popular

For freelancers shipping client work.

$29/month

Everything in Free, plus:

  • 3 active projects
  • 50 Patch runs / month
  • Up to 5 internal members

Agency

For teams managing many clients.

$99/month

Everything in Studio, plus:

  • 10 active projects
  • 250 Patch runs / month
  • 10 internal members

Agent execution runs on your own Claude, Codex, or Cursor account, so you only pay Patch for the workflow, not the tokens.

FAQ

Questions, answered

Everything worth knowing before you drop in the widget.

Get started

Stop relaying feedback. Start shipping it

One component in your app, zero accounts for your clients. The next piece of feedback comes back to you as a pull request.