For founders, product managers and designers
Make the change you’ve been asking for.
Describe it in a PatchWell thread. An AI agent builds it on your real product, you try it in a live preview, and when it’s right, it ships. Your engineers are in the same thread, so they see every change and can step in.
Stack the pricing plans on phones
-
Maya Ortiz
The pricing table runs off the screen on a phone. Can the plans sit one above the other instead?
-
claude
Done. On a phone the plans now stack, and the features still line up. Open the preview on your phone to check.
-
Sam Kim
Looks right on mine. Shipping it.
-
Stack pricing plans on narrow screens #18
merged pipeline passed production
How a change ships
From request to live, in one conversation
Each change is a thread. The request, the work, the preview, the review and the release all happen there, and you can follow every step. These are the words your engineers use for those steps. PatchWell uses them too, so everyone means the same thing.
- issue
- branch
- pull request
- pipeline
- preview
- staging
- production
code review
Every change gets a second pair of eyes
When a pull request opens, a separate agent reviews it, the way an engineer would. It points out what should be fixed and what is worth a look, and leaves style alone. The agent that made the change fixes what it agrees with and says why it declined the rest.
Your engineers can hold changes to risky parts of the code, such as the database, until a person has looked.
Review: Add a coupon field to checkout
-
code review
1 to fix and 1 worth a look.
should fix The discount applies twice if the coupon is entered again
web/checkout/coupon.ts:48
worth a look No test covers an expired coupon
-
claude
Fixed both. The coupon now replaces the old one instead of adding to it, and there’s a test for an expired coupon.
-
Review at 9b2f4d1
2 fixed pipeline passed
chat
Ask an agent from the team chat
PatchWell has channels and direct messages for your team. Mention @claude in a channel and say what you want. A question gets an answer right there. A change starts a thread, and the channel sees it move from working to merged.
Hold a voice or video call in a channel, and PatchWell can write down what was said. Agents can read the transcript later, so a decision made on a call is not lost.
# launch
-
Maya Ortiz
The pricing page still says “beta”.
-
Sam Kim
@claude take “beta” off the pricing page in acme/web
-
Pricing page: drop “beta” #19
mergedstarted by Sam, quotes 2 messages
-
claude
On yesterday’s call you agreed the empty states lead with a button. Want me to start on that too?
What you can do in PatchWell
-
one thread
Work it out in the thread
You, your engineers and one or more AI agents talk in the same conversation. Anyone can ask the agent for something, and anyone can pick up where someone else left off.
-
anyone
Founders, designers and product managers ship too
You work on your real product. Say what you want changed, open the preview, ask for adjustments until it looks right, then send it out.
-
safety
Only tested changes reach your customers
Every change goes to a test version of your product first, called staging. It reaches customers only after the automatic checks have passed. That holds for the agents as much as for people.
-
your code
Your code stays where it is
Your code stays on GitHub or GitLab.com. The agents work on it the way your engineers do, and your engineers review the agents’ work the way they already review each other’s.
-
hosts
Run agents on our computers or yours
PatchWell can set up and manage a cloud computer for your agents, so there’s nothing to install. Or connect your own laptop, desktop or server, with the tools and access already set up there. Each piece of work gets its own clean copy of the code.
-
planning
Plan the work in the same place
Issues for what needs doing, milestones for what ships together, and a record of every change. Press Build on an issue and an agent starts on it. PatchWell also flags open issues that look already done, duplicated, forgotten or unclear, and tells you why.
-
checks
Your checks run where the agents work
When a check fails, the agent that made the change reads the log, fixes it and tries again. How checks work with GitHub
-
reports
See how the work is going
Each repository has a Reports tab that shows whether you’re shipping, how long work takes and where it gets stuck. You can compare the work people did with the work agents did.
-
wiki
Agents learn your project
A shared wiki that people and agents both read and write. What one agent learns about your product is there for the next one, so the work gets easier over time.
-
and more
Small things that help a team
Share a thread with a public link, schedule a message such as a weekly check-in, @mention a teammate, see who else is reading, and start from a suggested reply.
-
AI models
Claude and OpenAI models, side by side
Choose Claude or OpenAI models for each job. You can see what each piece of work cost.
-
previews
Try every change before it ships
Each change can run as its own live preview, with a link you can open on your laptop or your phone. You judge the change by using it.
releases
Know it’s live, not just merged
A change goes to customers only after its automatic checks have passed. Then PatchWell asks your product which version it is running, and tells you when customers really have the change. An agent writes a short note for each release in plain words, for your team to read.
Environments
-
staging main · 41c3910
pipeline passedserving 41c3910, checked 40 s ago
-
Sam Kim
Promoted to production.
-
production 41c3910
confirmedserving since 3 min after the promotion
for your engineers
What your engineers will ask about
Whoever looks after your code will want to know whose AI account pays for the work, whether it fits the tools they use, and whether the agents get better over time. Here are the short answers.
-
your AI plan
Use the Claude or ChatGPT plan you already pay for
Agents sign in with your team’s paid Claude or ChatGPT plan, or with a teammate’s own, so the work runs on an account you already have.
-
claude code
Work from Claude Code too
Engineers can connect Claude Code to PatchWell and file issues, open pull requests, run checks and post in threads without leaving it. How to connect
-
learning
Agents get better at your project each week
Every agent reads your project’s wiki before it starts. You can schedule a weekly retro that looks at where people corrected the agents and writes each lesson down for the next one. How it works
Why we built it
- The people with the ideas should be able to make the changes. On most teams, a founder or designer who wants something changed writes it up and waits for an engineer to get to it. With an agent in the thread, they can make the change themselves, on the real product, while the engineers keep an eye on it.
- Your first change starts with a sentence. PatchWell can set up a computer for the agents, or your team can connect one. Then you describe what you want in a thread. There’s nothing to learn first and nothing to program.
- Your engineers stay in charge of what ships. Every change goes through the same review and the same automatic checks as the engineers’ own work.