What Flows just did
Based on your request to build Incident Response Runbook for Agent Mishaps, Flows created 4 implementation stages and 12 checks.
You asked for: Write and drill an incident-response runbook for agent mishaps: detection, immediate containment (kill switch), rollback, investigation via audit/traces, and a prevention feedback loop.. Flows generated 4 stages because the application requires Detection signals and reporting paths for agent mishaps; A kill switch: stop the agent and revoke its authority immediately; Containment and rollback procedures using checkpoints and audit trails. 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: No kill switch, so a misbehaving agent keeps acting while you scramble; Improvised response that makes things worse (deleting evidence, partial rollback); Investigations that cannot reconstruct what happened for lack of records.
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
4 stages · 12 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: Mishap signals enumerated with notification path…
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
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 4
Not startedDefine detection and the kill switch
You cannot respond to what you cannot detect or stop.
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
- Incident Response Runbook for Agent Mishaps
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.
Build detection and the emergency stop. DETECTION: enumerate mishap signals - blast-radius limits tripping, security events (blocked/escalated actions spiking), anomaly flags from observability (runaway cost, error bursts), audit-trail alerts on sensitive-resource changes, and human reports; define where each surfaces and who is notified. KILL SWITCH: implement a single, fast action that immediately halts the agent loop (no more turns), cancels in-flight tool executions at safe boundaries, and revokes the agent's tool authority (all tools drop to blocked/ask) - reachable by an operator without a code change and, ideally, auto-triggerable by severe signals (e.g. blast-radius hard stop). Test the kill switch: trigger it mid-task and confirm the agent stops acting within seconds and cannot execute further tools.
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
Detection signals wired and a fast, tested kill switch.
Should not happen
- ✕No kill switch, so a misbehaving agent keeps acting while you scramble
- ✕Improvised response that makes things worse (deleting evidence, partial rollback)
- ✕Investigations that cannot reconstruct what happened for lack of records
- ✕Postmortems that assign blame and change nothing structural
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…
- !No kill switch, so a misbehaving agent keeps acting while you scramble
- !Improvised response that makes things worse (deleting evidence, partial rollback)
- !Investigations that cannot reconstruct what happened for lack of records
- !Postmortems that assign blame and change nothing structural
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
The kill switch leaves in-flight actions running. It must cancel at the next safe boundary AND revoke authority so queued/next calls are blocked - stopping new turns is not enough if a destructive call is already dispatched.
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.