Recovery
Finished steps stay recorded after a restart. The interrupted step follows its own recovery rules, so a write with an uncertain outcome may need your decision.
Read the docsGive an agent a job. Keep track of the whole thing.
A request becomes a job you can follow: what the agent tried, what it is waiting for and what it returned.
Illustrative workflow using your configured tools, not a captured run.
Your request
“Why is checkout slow?”
- 01
Receive the request
- 02
Read the logs
- 03
Check the findings
- 04
Return a report
Result ready
You get findings to review, with the steps the agent took to reach them.
oz0’s default runtime runs the agent’s model and tool loop, keeping the job, controls and history together.
What you can do
Waiting
Let a workflow wait for a person or an event, such as a finished test run. No model runs during that workflow wait.
Read the docsDelegation
Split a bigger task between agents on suitable machines. Their jobs stay connected to the parent, with shared limits and a combined result.
Read the docsMonitoring
See the steps, costs, approvals and result in one job history. Follow it in oz0 Console, the web interface, or from your own app.
Read the docs