VVibeFix

The deal, in plain words

VibeFix reads the code behind an app you own, works out why something is broken, makes the smallest change that fixes it, and sends that change back to you as a pull request on GitHub. This page is what you and we are agreeing to. Last updated 22 August 2026.

This is an early, invite-only release. It is not finished software. Things will break, results will sometimes be wrong, and features will change without notice. Do not use it on anything you cannot afford to have broken, and keep your own backups.

1. Your account

You need an invite code to create an account, and one email address gets one account. You are responsible for what happens under it, so use a password you do not use anywhere else — we require at least twelve characters. Tell us at help@vibe-fixer.com if you think someone else has got in, and we will end every active session on the account.

Do not pass your invite code around. Invites are how we keep this small enough to support properly while it is still early.

2. What you point it at

Only connect repositories you own or are allowed to change. When you connect GitHub you choose which repositories VibeFix can see, and you can narrow or revoke that at any time from your GitHub settings — we would rather you granted it one repository than all of them.

Do not use VibeFix to build or repair anything illegal, anything designed to harm or deceive people, or anything you would be embarrassed to have us read. A person may read a conversation when something goes wrong.

3. What we do to your code, and what we will not do

Your repository is copied into a workspace that belongs to your project alone, and the changes happen there — not in your repository. The result is delivered as a pull request for you to look at and merge.

We will not push to your branches directly unless you have explicitly turned that on for a project, and even then only when the change is small and passed its checks. If anything about the situation is unclear — an unconfirmed branch, a check that did not run, a change touching a lot of files — it waits for you instead of guessing.

You approve every change that reaches your project. That is the whole shape of the product, and it does not have an override.

4. What "fixed" means here, exactly

A repair is checked with a type checker and a linter. It is not checked by running your app, because the environment repairs happen in cannot start one. So "verified" means the code compiles and passes lint — it does not mean somebody watched your app work.

Read the pull request before you merge it. The change was written by a language model, and while it is reviewed by the system that produced it, that is not the same as a person who knows your product having looked at it.

5. Limits

There are caps on how many projects an account can create and how many repairs it can run in a day, and a single repair stops after fifteen minutes whether or not it has finished. These exist so one account cannot exhaust the machines everyone else is sharing. We may adjust them, and during this early period we may pause an account that is making the service unusable for others.

6. Cost

VibeFix is free during this invite-only period. Every repair costs us real money in model usage, which we record per project. If that ever changes we will tell you before it applies to you, not after.

7. Your work belongs to you

Your code is yours. Your conversations are yours. Nothing you bring here becomes ours by bringing it here, and we do not claim any rights over the changes VibeFix produces for you.

We do learn from how repairs go — whether an approach worked, how long it took, which instructions helped. That is how the service gets better at its job. What we keep from this and what we do not is set out in the privacy notice.

8. No warranty, and the honest version of why

VibeFix is provided as it is, with no guarantee that it will work, be available, or produce a correct result. We are not liable for damage caused by a change you merged, for work lost, or for the service being down.

That is a standard clause, and here is the specific reason it is not boilerplate: the thing making the changes is a language model. It is often right and sometimes confidently wrong. The pull request exists so that a wrong answer costs you a review rather than your project.

9. Ending it

You can stop at any time and ask us to delete your account by writing to help@vibe-fixer.com. We will delete it and the projects under it. We can end your access if you break these terms, and other than in an emergency we will tell you why.

10. Changes to these terms

If we change anything that matters we will say so on this page and change the date at the top. Continuing to use VibeFix after that means the new version applies.

11. Getting hold of us

help@vibe-fixer.com reaches a person. It is the same address for a bug, a complaint, a deletion request, or a question about anything on this page.