What Flows just did
Based on your request to build Build Real Web App Authentication with Sessions and Protected Routes, Flows created 9 implementation stages and 39 checks.
You asked for: Create real signup, login, session persistence, logout, password reset, and protected dashboard routes that work across refresh and properly handle errors.. Flows generated 9 stages because the application requires Implement email and password signup with confirm password validation; Implement login and logout with real authenticated user state; Persist session across page refreshes. Each stage tells your AI builder what to do, tests whether it actually worked, and gives a repair instruction when it fails. These checks are designed to catch: Creating signup and login forms that do not connect to a real auth provider or backend; Pretending session persistence exists while user state resets on refresh; Allowing direct access to protected routes by URL when logged out.
Example failure
The form reported success, but no database record was created.
What Flows does
Flows detects the failure, generates a repair instruction, reruns the test, and stores the passing evidence.
Stages — Plan → Build → Test → Fix → Prove → Ship
9 stages · 39 checks · progressive disclosure — open a stage for details
Copy to external builder
Copies a prompt for Claude/Cursor/etc. Records prompt_copied only — not execution, commits, or checks.
Execute through Oort
Requires Sign in with Oort + a provider connection (BYOK). Keys stay on Oort. A model name in the dropdown is not the same as a live connection.
Next
Check off: A real auth provider or backend auth implementat…
Add a proof note on each check — a checkbox alone is weak proof.
Probes & advanced tools are under “More verification tools”. Experience level: Settings.
Project (saved with proof)
Project binding: Unbound — complete project binding before trusting this run · missing repositoryUrl, repositoryStartCommit, environment, stack
More verification tools (probes, timeline, adapters)Show
App persistence (create → read → assert token)
Body template: {"probe":"{{token}}","title":"flows-probe-{{token}}"}. Needs CORS-readable public create/list endpoints (or inconclusive). Badge only when create→read→refresh finds the token (detects false success).
Two-account authorization (User B cannot see/change User A)
Authorization evidence source: Cross-account ownership test (trust level 5/6). These are not equivalent. Unauthenticated probe alone is weaker (source: unauthenticated API probe). Tokens stay in this browser session only — not uploaded to Flows servers.
Generated edge-case tests (review / approve)
- api_probe Submitting the form empty is rejected with a clear error
- api_probe Each required field can be omitted and fails validation
- api_probe Malformed email is rejected
- api_probe Malformed phone is rejected when phone is collected
- api_probe Duplicate submission does not create two records
- api_probe Double-click submit creates only one record
- false_success_probe Failed request does not show success
- browser_automation Refresh during submission does not leave corrupt state
- api_probe Oversized input is rejected
- api_probe Unsafe strings do not execute or break storage
- api_probe Logged-out users cannot open protected pages
- api_probe Protected API rejects requests without credentials
- api_probe Expired session cannot mutate data
- browser_automation Logout in one tab invalidates mutations from another
- cross_account_probe User B cannot see or change User A’s data
- cross_account_probe Participant cannot call coach/admin endpoints
Generated from this route’s signals — you approve; you do not invent security tests.
Content probe (GET body contains text)
In-product content probe reads response text when CORS allows — not full DOM/click automation. Playwright script is optional and external.
Proof strength
thin · 0/100
Heuristic from notes + probes + gates — not a production certification.
Verification adapters
- ● Deploy URL probe · idle
- ● API path probe · idle
- ● Authz probe (unauth → 401/403) · idle
- ● Browser persistence · idle
- ● App persistence (create→read) · idle
- ● Content / body text probe · idle
- ○ In-product Playwright DOM · not embedded (download external script)
Filled circles = available here. Empty = not shipped. Probes are not a production audit. Adapter docs
Step 1 of 9
Not startedSet the auth architecture and choose the real persistence layer
Force the AI builder to define and implement a real authentication approach before generating UI.
If your app already uses a stack like Supabase, Firebase Auth, Auth0, Clerk, NextAuth, or a custom backend, tell the builder to use that existing stack instead of inventing a fake one.
Flows keeps plan, checks, failures, and next steps connected
Your AI tool writes or changes the code
Repository grounds the plan only after inspect
Checks always carry a validation tier
How this plan was created
Plan from project details
Flows creates steps using the goal, requirements, stack, platform, and details you provide.
- Project description
- Selected template / route
- User-entered stack
- Constraints and notes
- Build Real Web App Authentication with Sessions and Protected Routes
No repository inspection implied. Connect and inspect a codebase to ground steps in real files.
Codebase access
Checking GitHub…
Or paste a repository URL manually
Use these instructions in Claude, ChatGPT, Cursor, Emergent, or another builder.
Inspect this codebase and implement a real authentication foundation using the existing stack where possible. I need email/password signup, login, logout, session persistence across refresh, protected dashboard routes, duplicate email handling, password reset, loading states, error states, and mobile responsive UI. Do not build placeholder forms. Use a real auth provider or real backend persistence, define where user state lives, define how session restoration works on app load, and wire the routing strategy for protected pages.
Project context
Copies the project goal, technical details, current step, previous progress, and checks so your AI tool understands what it is working on.
Expected after this step
The app has a real auth strategy selected and wired into the project, with a clear user/session state source and route protection plan.
Should not happen
- ✕Creating signup and login forms that do not connect to a real auth provider or backend
- ✕Pretending session persistence exists while user state resets on refresh
- ✕Allowing direct access to protected routes by URL when logged out
- ✕Handling duplicate email or invalid credentials only in console logs instead of showing UI errors
Verify gate — prove this step works before continuing
Do not move on until every check is true. Add proof notes — a checked box alone is weak proof. Checks are manual by default; deploy/API probes live under “More verification tools” and do not auto-check boxes.
Do not continue if…
- !Creating signup and login forms that do not connect to a real auth provider or backend
- !Pretending session persistence exists while user state resets on refresh
- !Allowing direct access to protected routes by URL when logged out
- !Handling duplicate email or invalid credentials only in console logs instead of showing UI errors
- !Storing tokens or passwords insecurely or exposing sensitive auth logic in the client
- !Adding a reset password screen that is not connected to a real reset mechanism
Repair path — if this step fails
Use the Repair Prompt when a verify gate fails. Loop: Detected → Diagnosed → Repair issued → Changed → Retested → Resolved
Show repair prompt textShow
You built forms without proving real auth integration. Replace any mock auth logic with a real provider or backend implementation for signup, login, logout, session restore, password reset, and protected routes. Show exactly where the real session comes from and remove all fake success redirects.
Your notes for this step
Definition of Done
Final route-level requirements. Manual checks — separate from per-step verify gates. Completing step gates does not auto-check these. Route completion is not a production-ready claim.