About Ctrl+Z Therapy and how we test

Who it is for

People who built something with AI and got stuck: founders, makers and small teams who are not full-time programmers. That is why every case starts with what you would notice, not with the bug's technical name.

How we build each case

• Each case is a small demo built on purpose with one bug, fake users and fake data.
• Nothing is taken from a real person's app. The cases are common kinds of bugs, not reports of real incidents.
• Every page is labelled “Controlled demo · fake data”, and the code on screen is simplified.

How we test the fix

• For cases 003, 004, 005, 006, 007, 008, a scripted test sends the same requests to the demo before and after the fix. The tables show the results as they came out.
• When something was not part of the test, the table says “Not tested” instead of guessing.
• For cases 001 and 002, the before and after are shown in the demo video only. Those pages say “What the demo shows”, and you should test your own app before relying on them.
• Each page shows when its demo was built and when the page was last reviewed.

What we never do

• We don't scan or test other people's live apps without permission.
• We don't publish anything you send us without your explicit permission. You can choose to be named, stay anonymous or keep it private.
• A case file is not a security audit or a guarantee. It explains one kind of bug and how to check for it.

When you send in your app

We read every submission and reply with a diagnosis and next steps, then help fix it for free. No code knowledge or repo is needed to start. See what happens to what you send, or send it in.

Corrections

If something on this site is wrong, tell us through the intake form or an Instagram DM to @ctrlztherapy. We fix it and update the page's “Last reviewed” date.

Changelog

• 23 Sep 2026: site launched with 8 case files, the 10-minute checklist and the intake form.