One harness between the agent and everything it touches.
The agent proposes. The harness decides what runs, waits for a person when it should, and checks the finish.
1
Where it sits.
Between the agent and your files, shell, network and database. Inside the task boundary the agent works freely; anything past it stops here.
Every action the agent takes passes the harness first.
Every action passes the harness first. The edit and the tests are inside the task boundary and go through. The schema rewrite and the .env upload are outside it, so they stop at the harness and never run.
2
Every request gets one of four answers.
The agent never decides this itself. The harness does, before anything runs.
-
Allowed
Inside the task boundary. It runs.
-
Stopped
Outside the task. It never runs, and the agent gets the reason.
-
Held
Risky, like a push. It waits until a person says yes.
-
Checked
“Done” is a claim. Tests and the diff have to agree first.
Questions teams ask first.
How do we get access?
OopsAI is available on request. Write to us from the form on the homepage with a line about your workflow, and we’ll set up a conversation about access and integration.
Does it replace our agent framework?
No. The harness wraps the agent workflow you already run. Tell us which framework and runner you use and we’ll discuss how it fits.
Where are boundaries enforced?
The harness decides before each action. The runner and its environment enforce the file, tool and network access that decision allows. We agree on those controls together during integration.
What goes into the trace?
The task, each request the agent made, the decision and the outcome. Enough to explain a run, without collecting more of your code or data than the workflow needs.
What happens to my contact details?
The site doesn’t collect or send anything itself. The contact form only opens a draft in your own email app, addressed to us. We use what you send only to reply. There are no analytics, trackers or cookies. To have your messages deleted, ask in any reply. Our host keeps standard server access logs.