Make the small product changes
without waiting for a sprint.
Refinar runs a copy of your app from GitHub. Describe a change, watch it made in a live preview, then publish it or send it to engineering as a pull request.
The changes that never make the sprint
Obviously right, never urgent
Every product has a list of changes that are obviously right and never urgent: a confusing label, an empty state that says nothing, a settings page in the wrong order. Each one is an hour of a developer's time, so each one waits behind work that matters more.The person who noticed it makes it
The agent works on a copy of the app started from your repository, so you judge the result in the product itself rather than in a mock-up, and customers see nothing until it's published.A change, from request to review
01
Describe it, or point at it
Type the change in plain words, or use Select an element in the preview and click the heading, button or section you mean. Screenshots and text files can go in with the request.
02
Watch it happen
The preview updates as the agent works. For wording, colour, size and alignment you can also edit the preview directly and apply the edits.
03
Rewind what you don't like
Any message can be rewound until the change is published, so trying an idea is cheap.
04
Publish, or send it for review
Publishing merges the change into the app's main branch. Send for review marks the pull request ready and routes it to a reviewer you name, or to anyone on the team. If the app is set so changes need approval first, sending for review is the option you'll have.
What the agent won't do on its own
Three kinds of change stop the agent
Editing who can sign in or what they can see, changing what customers are charged, and deleting data. It also stops before switching on anything that sends to the outside world, like scheduled emails or webhooks, and when it needs a key the app doesn't have. Restyling a sign-in or checkout page is fine. Changing how either one works is a developer's call.When it stops, you choose
Build the part that's safe, or hand the whole thing to a developer, which files a request with the details and opens a GitHub issue. It then sits in the developers' review list inside Refinar.Prototype on the real product
Prototypes are for ideas you aren't ready to ship. Start one on your live app and it uses the real screens and design system, with stand-ins where the idea needs sign-in or prices it doesn't have yet, each one flagged.
A prototype never opens a pull request. When the idea holds up you apply it to the app as a normal change, or hand it to a developer with an implementation plan the agent writes: what it's for, what changes, how to build it properly, the tests and the risks.
Who can do what
- Describe changes and watch them built
Members: Yes
Developers, admins and owners: Yes
- Publish a finished change
Members: Yes, unless the app needs approval first
Developers, admins and owners: Yes
- Approve a change sent for review
Members: No
Developers, admins and owners: Yes
- Publish a change the agent stopped on
Members: No, it goes to a developer
Developers, admins and owners: Yes
- Connect services and set keys
Members: No
Developers, admins and owners: Yes
- Write Rules for the AI and choose who publishes
Members: No
Developers, admins and owners: Owners and admins only
| Members | Developers, admins and owners | |
|---|---|---|
| Describe changes and watch them built | Yes | Yes |
| Publish a finished change | Yes, unless the app needs approval first | Yes |
| Approve a change sent for review | No | Yes |
| Publish a change the agent stopped on | No, it goes to a developer | Yes |
| Connect services and set keys | No | Yes |
| Write Rules for the AI and choose who publishes | No | Owners and admins only |
Roles are set per team by an owner or admin, and members never need a GitHub account.
Questions product managers ask
Do I need GitHub or a terminal?
No. An owner or admin connects the app once through Refinar's GitHub App, and every change goes through the team's connection. Members install nothing.
Will engineering trust it?
Every change is a pull request in the team's own repository, and the reviewer gets the original request and the running preview along with the diff. An owner or admin can also set the app so nothing goes live without a developer's approval, and give the agent written rules for what it may touch.
How is this different from Claude Code or Codex?
Those are coding agents a developer drives on their own machine or in a cloud session, and they hand back a diff. Refinar starts the app for you and gives you the preview to judge (Claude Code for product managers covers that route honestly).
What does it cost?
From $50 a month for 500 credits, which is about 100 requests, with unlimited apps and 20 teammates included (pricing).
Product details are from Refinar's app and documentation, checked on 7 October 2026. For a step-by-step guide to publishing, see publish a change, or share it for review.