Zeroshot Graph Engine
Split a task into focused work, independent checks, and explicit repair paths.
How a run works
A graph is the workflow: which steps run, what each step receives, and what happens next. Agents do the work and return structured results. The engine validates those results, follows the graph, and enforces its limits.
- WorkImplementChange files and run tests.
- Independent checksReview the result
- Task criteria Fresh conversation
- Code quality Fresh conversation
- Checks passDeliverPublish the result using the profile's delivery step.
If a check fails, findings return to the worker. Repair, then review again.
If the repair budget runs out, this loop stops before delivery.
This is one work/review loop. Graphs can also branch, run checks in parallel, or route evidence to a decision. Your profile chooses the steps, models, session behavior, and delivery: a push, pull request, merge, or review comment.
Why separate the work and review?
A reviewer in a fresh conversation inspects the task and current files without inheriting the worker's chat. That can reduce anchoring on the worker's explanation.
Explicit inputs and findings keep handoffs focused. The worker can keep its conversation across repairs when continuity helps; reviewers can start fresh each time. These are runtime choices. Fresh context does not guarantee a correct result: acceptance criteria, tests, and the reviewers' coverage still matter.
Agents share the run's files, so separate conversations do not isolate filesystem writes. Coordinate parallel changes. Active Memory can supply selected lessons across runs without restoring an old conversation.
Configure or author a workflow
Platform profiles save the graph and runtime settings together. An environment supplies preparation and network policy. Platform provides the machine, credentials, queue, and run history.
Graph | Steps, typed data, conditions, and loop bounds |
|---|---|
Runtime | Harnesses, models, and fresh or continuing sessions |
Connections | Provider choices and credential declarations |
Build a complete example with the review-loop tutorial. The Zeroshot documentation also covers CLI usage and self-hosted targets. These links follow the release Platform runs.