← All stories · Auth, sessions & access

Make AI-written login actually log users out

Auth took 2 minutes to generate and 2 hours to fix · X · @mustaphaDevFS · Oct 2026

A builder had AI write their login flow almost instantly, then lost an afternoon working out why users were never logged out.

The honest numbers

As stated by the source. Not independently verified.

Lesson

Ask the AI to explain session expiry and logout before you accept auth code, then test logging out and waiting for a session to expire.

Fix prompt

Copy this into your own AI tool (Cursor, Lovable, Claude Code, Bolt…). It's general guidance written by us. Review what the AI suggests before applying it.

I'm a beginner building an app with my AI coding tool. Please review how login, sessions and access control work in my project. 1) Explain in plain English how a user signs in, how long a session lasts and what happens on logout. 2) Check that sessions expire, that logout really ends the session on the server, and that every API route and database query checks the user is allowed to see that data (not only the UI). 3) List each problem you find with the file name and a suggested fix, most serious first. 4) Give me a short manual test plan: log in, log out, wait for expiry, and try to open another user's data with a second account. Don't change anything until I've approved your plan. Never ask me to paste API keys, passwords or .env contents; tell me where to check them myself.

Source: X ↗

The Honest Build. Real stories, not hype.

Every week: real stories of what building with AI actually took, the one lesson worth keeping, and the security slip-ups to avoid. Free, unsubscribe anytime.