Example workflow you can build
Turn a failing test into a reviewable fix.
An agent investigates the failure and prepares a pull request. Reviewers and your CI process decide what ships.
01 The problem
Your system
"Checking out with an empty cart crashes our web application."
Webhookstarts an oz0 job
02 The agent investigates
- Tool rules & approvals
- Model budgets
- Job history
Your task plugin
Runs on your oz0 node
Connector tool · Repository
Reading the checkout API contract.
Result: HTTP 400; no payment call.
Connector tool · Test runner
Uses a fake payment gateway.
Your systems
- Empty cart
- Checkout API
Result: HTTP 500 instead of 400.
Connector tool · GitHub
Adds empty-cart validation and a test. Links the fix to the original failure.
03 People decide
Your process · GitHub and CI
CI must confirm HTTP 400 and no payment call before the patch can merge.
04 The outcome
Approved
Your systems
Merge and release under your existing rules.
Verify the deployed behavior; link evidence to the issue.
Denied
Review rejected or tests failed.
Agent revises the patch; review runs again.
Both possible outcomes are shown. No real actions run.
How these parts fit
- Plugin
- Installable package of agents, tools or instructions.
- Agent
- Uses your model to choose tool calls.
- Connector
- Plugin providing tools for an outside system.
- Tool
- Exposes actions the agent can call.
- Webhook
- Notification that starts configured work.
Use existing plugins or build these integrations. Plugin docs
Writing a patch grants neither merge rights nor permission to release it.
What you connect
Connect repository, CI and deployment tools, a model, and a sandbox with the project’s test dependencies and fake payment gateway.
Build an agentA starting point
pr-reviewer inspects changes and runs supported tests. Creating patches and coordinating releases require a separate workflow and tools.
DocsThese starters are documented; publication varies. See oz0 Hub for availability.