Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I used an AI tool to fix my app and now it is more broken than before

Short answer

Stop asking the tool for more changes, because each one stacks on the last. Find out whether there is a saved earlier version: Git keeps the history of changes, and builders such as Bolt keep a version history you can restore. Note that restoring code does not roll back a database. Then have a developer find what changed.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I pasted an error into an AI assistant, applied the answer, and a different error appeared.
  • After several rounds the app no longer starts, or a feature that worked is gone.
  • I do not remember what was changed, or in what order.
  • I have no copy of the version that worked.
  • The tool keeps suggesting new fixes, and each one adds more problems.

Why does this happen?

  1. The tool sees only what you give it

    An assistant answers from the code, error message and description in the conversation. If the real cause sits in a file, a setting, the database or the server that you did not share, the fix can be aimed at the wrong place. The tool is not at fault for this; it is a limit of how it is used.

  2. Each change builds on the last one

    After several answers applied one after another, the code may differ from anything you could describe. A second change can undo or conflict with the first, and the original error is then hard to find.

  3. A history of versions is what lets you go back

    Git is a version control system that tracks the history of changes, and you can recover any earlier version of a project. If the project was never put under version control, there may be nothing to go back to.

  4. App builders keep their own saved versions

    Bolt saves a version after every prompt that processes, and you can open Version history, preview an older version and restore it. Bolt also states that restoring an earlier project version does not change your current Bolt or Supabase databases, so data changes made since then stay.

What can I do about it today?

  1. Stop changing thingsDo not apply any further AI suggestions for now. Every extra edit makes it harder to see what went wrong.
  2. Copy the whole project somewhere safeMake a copy of the project folder, or download the project from the builder, and keep it as it is now. Nothing is deleted by copying.
  3. Look for an earlier working versionCheck whether there is a Git history, a version history in your builder, or a backup from your hosting company. Only look and write down what exists; do not restore anything yet.
  4. Write down what changedNote what worked before, what is broken now, the exact error message and roughly what you asked the tool to do. Screenshots help.
  5. Do not touch the live databaseIf the app has real customer data, do not run commands or scripts a tool suggested against it. A code restore does not undo data changes.
  6. Tell customers only what is neededIf the live app is affected, a short notice that you are looking into a problem is enough.

When should I bring someone in?

  • The app is live and customers or payments are affected.
  • You cannot find any earlier working version.
  • The tool suggested changes to the database, logins or payments.

How do I handle it?

  1. Secure a copy firstI copy the current state and any history before touching it, so everything I do afterwards can be undone.
  2. Find the last good pointI use the version history, backups or file dates to find the last state that worked and compare it with now.
  3. Separate the changesI list what the assistant changed and test each change, keeping the useful ones and dropping the harmful ones.
  4. Repair and testI fix the real cause, test the main paths and release with a tested rollback ready.
  5. Set up a safer way to workThe project goes under version control with a short rule: every change is saved first, and every AI suggestion is reviewed before it goes live.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Are AI assistants bad for code?

No. They can write and explain code, and many developers use them. The problem is applying changes without a saved earlier version and without checking them, which is a process issue.

Can the original version be restored?

Only if some copy exists: a Git history, a builder's version history or a hosting backup. Restoring code is not the same as restoring data, so the database needs its own check.

Should I keep using the AI tool?

That is your choice. If you do, save a version before each change and have somebody review what goes into the live app.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.