How Fix it for me works

On Pro and Business, Heedza can do more than tell you what broke. When it finds a problem it knows how to fix, the alert has a Fix it for me button. Press it and Heedza writes the fix, then waits for your OK. Nothing in your app changes until you approve it.

What it can fix today

  • Problems on the pages Heedza checks for you, such as a sign-up, log-in or checkout page that stopped working.
  • A file that should not be public, such as a database backup. Heedza removes the file from your code. It does not open or read the file.
  • A security setting that your site stopped sending. Heedza puts back four browser settings: always open with https, stop other sites showing your pages inside theirs, stop browsers guessing file types, and limit what other sites learn about where visitors came from.

Other alerts, such as downtime, an expired certificate or a leaked key, still come with a fix you paste into your AI tool. Those have to be fixed at your host or by you.

1. Connect GitHub (once)

Heedza never connects to, or logs in to, the AI tool you built your app with (such as Lovable, Bolt, Replit or v0). To check your app, Heedza only needs its web address. The fix button is different: it needs your app's code on GitHub.

  1. In Heedza, open your app and press Connect to GitHub.
  2. GitHub opens and shows the Heedza app and what it may do. Choose your account, then Only select repositories, and pick the one repository that holds this app. (A repository is the folder on GitHub that holds your app's code.)
  3. Press Install, then Authorize. This lets Heedza confirm that the GitHub account is yours.
  4. Back in Heedza, confirm the repository and press Check my connection.

You don't create or paste any password or access code. Heedza can read the files a fix needs and open fixes in the repository you picked. It can't change your GitHub settings, secrets or workflow files. It never reads or changes files that hold keys or passwords (such as .env), package lists, or database files.

2. Press Fix it for me

When Heedza finds a problem it can fix, the alert (by email, Slack or Telegram) has a Fix it for me button at the top. Below it is Or fix it yourself, with the steps and the fix prompt to paste into your AI tool, as before. Use whichever you like.

Fix it for me opens a short page on heedza.com: press the button there to start. In Telegram the button starts it right away and answers "Working on the fix, about a minute". Pressing twice does not start two fixes. If you've reached a limit, or fixes are paused, the page says so and nothing starts.

3. You get a fix to approve

Heedza writes a small fix and opens it on GitHub as a pull request: a proposed change to your code that GitHub keeps on the side until someone accepts it. You get a Fix ready to approve message with what broke, why, what the fix changes, which files change and by how many lines, and Review and approve and Reject buttons.

If the fix touches sign-up, sign-in or payment code, the message says Please review and names what it touches. Read those changes with extra care.

Review and approve opens a page with the full change. Nothing happens until you press Approve and merge there. Heedza checks the fix on your host's preview first, if your host makes one, then merges exactly the change you saw (it is added to the main copy of your code) and starts the second check. Reject closes the pull request and your code stays as it is.

4. The second check

After you approve and the change is added to your main code (GitHub calls this a merge), your host needs a few minutes to put the change on your live site. Heedza looks at your site 2, 5, 10, 20, 35 and 50 minutes after the merge. Once the change is live, it runs the check that found the problem, Homepage loads, and every other page Heedza checks for this app. Then you get a second message:

  • Fixed. The problem is gone and all checks passed. The message lists them.
  • Still there. The problem was still there after 50 minutes. The message has an Undo button.
  • Something else stopped working. Another check failed twice in a row after the fix went live. The message says which one and has an Undo button.
  • Merged, not live yet. Your site did not show the change within 50 minutes. Heedza looks once more about 3 hours later. If your tool needs you to press Publish (Lovable does), press it.

5. How to undo a fix

  • In the second message, press Undo. The link works once, for 7 days.
  • Or open the fix in your dashboard (Fixes, then the fix) and press Undo this fix. This works for as long as the fix is merged.

Undo opens and merges a new pull request that puts the changed files back to how they were before the fix. You get a message when it's done.

6. What is sent to the AI

To write a fix for a page problem, Heedza sends our AI provider, Anthropic, the problem it found and the text of the files needed for the fix (at most 12 files). Under Anthropic's commercial terms, this text is not used to train its models and is deleted from its systems within 30 days.

Heedza never sends files that hold keys or passwords (such as .env), key files, package lists or database files. Before sending any file, Heedza removes text that looks like a key or password, and it does not send files that are mostly keys or passwords. Fixes for a public file or a security setting don't use the AI at all.

7. How to stop it

  • For one app: Fixes, then next to the app, press Fixes on · turn off.
  • For everything: press Disconnect in Heedza, then also uninstall the Heedza app on GitHub (GitHub, Settings, Applications, Heedza, Configure, Uninstall).

How many fixes you get

The fix button is part of the Pro and Business plans. Free, Solo and Starter don't include it; you still get a fix to paste into your AI tool with every alert.

  • Pro: 15 fixes a month, 30 fix attempts a month, 5 a day.
  • Business: 50 fixes a month, 100 fix attempts a month, 10 a day.

What counts as an attempt: each time Heedza starts working on a fix, also when it ends up not opening a pull request (for example because the change would be too big). A fix counts when Heedza opens its pull request, whether or not you approve it.

When a limit is reached, the Fix it for me page says so and nothing starts. You still get every alert with the copy-paste fix. Daily attempts start again at 00:00 UTC; monthly ones on the 1st at 00:00 UTC. On a very busy day, Heedza may hold new fixes for all customers until the next day. At most 3 fixes can be in progress for one app at a time.

Too many tries on a fix link: if a link is pressed many times in a few minutes, Heedza shows "Too many tries" for a short while. Wait about 10 minutes and open it again.