From generated code to code you can keep.

Refract reads the project, finds what will get messy, and prepares a cleanup you approve. You never leave GitHub to decide.

Get started

A simple loop

1

See the project

Refract looks at the software as a whole, so a change in one screen can respect the rest.

2

Find what will hurt later

It looks for the patterns that show up when code is generated quickly: copied logic, tangled screens, leftover state, structure that won’t age well. If something sensitive was left in the code — like a credential — it tells you. It does not quietly “fix” secrets.

3

Clean what it can

When the cleanup is safe, you get a concrete change to approve. When it isn’t, you get a clear explanation instead of a guess.

4

Check, then remember

After you approve, Refract applies the change and looks again. Over time you can see whether the project is getting cleaner — or still shipping the mess.

Decide on GitHub. Use the website for the rest.

On GitHub

On the website

The website is not a second place to accept cleanups. The decision stays next to the code.

You’ll see one of a few honest results

Still working

Wait. This is not a pass.

Looks clear

Nothing from Refract needs you on this change.

Cleanup ready

A safe cleanup is prepared. Approve it on GitHub.

Have a look

Something matters, and Refract will not change it for you. Read the explanation.

Something went wrong

Analysis failed. Refract will say so. It will not paint a fake success.

What “cleaner” means in practice

On React and TypeScript projects, Refract is especially good at the leftovers of fast generation:

data fetching mixed into the interface

the same logic written twice

state that is never really used

effects that don’t clean up after themselves

missing timeouts and missing error handling at the edges

screens doing work that belongs elsewhere

Some of that, it can clean for you. Some of that, it will only point out — on purpose. A bad automatic rewrite is worse than an honest note.

Live in minutes

1

Create an account

2

Install the GitHub App and pick repositories

3

Open a pull request

Create your account

Connecting GitHub does not sign you into Refract, and signing into Refract does not install GitHub access. Two steps, two jobs.

Will this fight my AI tools?

No. Keep generating. Refract is the pass that keeps the result maintainable.

Will it change code without me?

No. You approve. You merge.

Do I have to learn a new workspace?

No. Day to day, you stay on GitHub.