Skip to content

Core documentation

Build and review software through a graph

A Zeroshot graph records implementation, review, repair, and delivery as bounded execution steps. Its authored transitions determine which node runs next.

Run a first task Read the CLI reference

What a run contains

Three authored values determine execution:

  • a graph that defines control flow and typed state;
  • a runtime plan that binds each executable node to a harness, provider, model, and named connections;
  • an initial input that belongs to the caller and that Zeroshot checks against the graph before execution.

After validating those values, Zeroshot opens a durable ledger where it records each node result. Authored edges then route review, retries, and the final result.

flowchart LR
  I[Goal and source] --> A[Admission]
  A --> W[Worker]
  W --> R1[Acceptance review]
  W --> R2[Code review]
  R1 --> D{Both accept?}
  R2 --> D
  D -- no --> F[Bounded repair]
  F --> R1
  F --> R2
  D -- yes --> X[Result or delivery]

The built-in software-change template uses the route shown above. For work that does not need its review loop, use single-worker; custom graphs follow the same protocol contracts.

Choose where it runs

  • Local

Local mode works in the current Git worktree, keeps state on the same machine, and calls your installed Codex or Claude harness.

Install Zeroshot

  • Self-hosted target

The target image checks out source on infrastructure you control. Agent processes and the run ledger stay there as well.

Understand targets

  • Zeroshot Cloud

Cloud accepts the same graph and runtime plan through a managed target. Its documentation covers accounts, organization policy, and queue behavior.

Open the Cloud docs

Read more

How execution works describes the graph and reduction model. Read Runtimes and connections before choosing models or supplying credentials; Observe and control runs covers durable status and log streams.

The reference section is built from product-owned definitions:

  • CLI reference, generated from the Clap command tree;
  • Python API, generated from the SDK's public objects and docstrings;
  • Cluster API, generated from the checked-in OpenRPC contract and protocol schemas.

When reading about an installed release, choose its version from the header. Exact release paths do not change, while stable and dev move; Documentation versions defines the URL and manifest contract.