The step after AI writes the code
AI wrote it. Make it ready to ship.
Refract takes the code your AI tools produce and turns it into something cleaner, more consistent, and easier to keep — so the project doesn’t fall apart as it grows.
You approve every change. Refract never rewrites your project on its own.
interface code doing work that doesn’t belong there
leftover state and effects that only made sense in the moment
structure that made sense for one file, not for a product
Working code can still be a mess. You don’t need more generated code. You need the generated code to stay good.
Refract is what happens after the AI writes the code.
Not another list of complaints. A cleaner project.
export function Orders() {
const { data, loading } = useOrders()
const [data, setData] = useState([])
const [loading, setLoading] = useState(true)
useEffect(() => {
fetch('/api/orders')
.then((r) => r.json())
.then(setData)
.finally(() => setLoading(false))
}, [])
return <List items={data} loading={loading} />
}
Before it becomes the codebase
The result is code you can keep.
Cleaner
The obvious mess gets pulled out of the screens and put where it belongs.
More consistent
Repeated logic stops multiplying. The project starts to look like one product, not twelve first drafts.
Easier to change
You can add the next thing without stepping through a maze that nobody meant to build.
Still yours
Nothing changes until you say yes. You see what will happen. You keep the merge button.
It doesn’t just point at problems. It makes the code better.
1
It learns the project first
Refract looks at how the software is actually put together — not only the last file that changed — so a cleanup fits the project you already have.
2
It finds the mess AI tends to leave behind
Copied logic. Data fetching inside the interface. State that nobody uses. Effects that linger. Structure that will hurt as soon as the app grows.
3
It tells you what to clean first
When there’s more than one issue, you get an order that makes sense — not a wall of noise.
4
It can do the cleanup for you
When the change is safe and contained, Refract prepares it. You approve. It applies the change and checks that the project still holds together. If it can’t do the change safely, it says so, instead of guessing.
It shows up where the code is about to become the project.
Connect the repositories you care about. When new code is proposed, Refract reviews it in place.
One result. You decide.
Refract
Looks clear
Nothing from Refract needs you on this change.
Refract
Cleanup ready
A safe cleanup is prepared. Approve it on GitHub.
Refract
Have a look
Something matters, and Refract will not change it for you. Read the explanation.
You get one clear result:
Approve on GitHub. Stay in the flow you already have. Refract does not ask you to live in a second inbox.
Controlled. Visible. Reversible in practice — because you are still in charge.
You approve.
Refract never applies a change until you do.
It would rather stay quiet than be wrong.
If it can’t prove a problem, it doesn’t invent one to look busy.
If it can’t clean something safely, it doesn’t pretend.
You get an explanation, not a reckless rewrite.
It checks its own work.
After a cleanup lands, Refract looks again. A failed cleanup is never described as success.
It is not a chatbot rewriting your app.
The cleanups it applies are specific and constrained. Creative guesses are not “fixes.”
Three steps. Then it runs while you work.
1
Create an account
Email and password. That’s your Refract login — not a GitHub sign-in.
2
Connect GitHub and pick repositories
Install the Refract app on the projects you want cleaned. You choose which ones.
3
Keep shipping
Open a pull request like you already do. Refract reads the change in the context of the project. If a cleanup is ready, you approve it. Then you merge when you’re ready.
Installing the app is not the same as signing in. Your Refract account and your GitHub access stay separate on purpose.
For people who build with AI and still have to live with the result.
Individuals
You’re shipping a product with Copilot, Cursor, or the next model. The code comes fast. You want it to stay something you can maintain.
Teams
Several people generating at once. The repo is the shared memory. Refract is how that memory stays coherent.
Built for today
React and TypeScript on GitHub. That’s where this problem is loudest right now. Other stacks come when they’re real — not as a promise on the homepage.
Teams generating software need a step after generate.
Used by developers who build with AI on GitHub. Want to be an early team? Contact us
What Refract is not.
It is not an IDE. It is not a replacement for your AI coding tools. It is not a generic linter. It is not a bot that leaves twenty comments on every line.
It will not reorganize your entire product overnight. It will not auto-fix every security issue. It will not merge for you.
It will make the AI-generated parts of a React and TypeScript project cleaner, clearer, and easier to keep — with you in control.
Generate the code. Don’t inherit the mess.
Create an account, connect GitHub, and let Refract take the first drafts the rest of the way.