What Flows just did
Based on your request to build From CLI Harness to Product, Flows created 5 implementation stages and 15 checks.
You asked for: Productize my agent harness: named sessions with resume, layered configuration, first-run experience, and clean packaging.. Flows generated 5 stages because the application requires Persistent sessions: every run saved, listable, and resumable by ID; Layered config: defaults < config file < environment < flags; A first-run flow that validates credentials and writes a starter config. 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: Resume that replays a chat log but loses tool state and working directory; Config spread across hardcoded values nobody can override; First run failing cryptically on a missing API key.
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
5 stages · 15 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: Saved after every turn, not on exit
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 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
- cross_account_probe URL/body ID tampering cannot cross tenant boundary
- api_probe Create then refresh still shows the record
- api_probe Edit then refresh keeps the edit
- api_probe Delete then refresh removes the record
- api_probe Nonexistent record ID fails cleanly
- cross_account_probe Cross-user record identifier is rejected
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 5
Not startedImplement persistent sessions
Sessions turn a script into a tool people trust with long work.
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
- From CLI Harness to Product
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.
Add session persistence to the harness. Each session stores: a generated ID and user-friendly title (derived from the first task), the full message history, todo/plan state, the working directory, model and config snapshot, timestamps, and status (active, completed, escalated, cancelled). Store as JSON files under a sessions directory (or SQLite if already available). Implement: session creation on run start, incremental saving after every turn (crash-safe), `list` showing recent sessions with title/status/age, and `show <id>` printing a readable transcript summary. Verify a killed process leaves a loadable session file.
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
Crash-safe session persistence with list and show commands.
Should not happen
- ✕Resume that replays a chat log but loses tool state and working directory
- ✕Config spread across hardcoded values nobody can override
- ✕First run failing cryptically on a missing API key
- ✕Session files leaking API keys into plaintext on disk
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…
- !Resume that replays a chat log but loses tool state and working directory
- !Config spread across hardcoded values nobody can override
- !First run failing cryptically on a missing API key
- !Session files leaking API keys into plaintext on disk
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
Sessions only save on clean exit. Move the save into the turn loop (write temp + rename for atomicity) so any crash loses at most the in-flight turn.
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.