Zeroshot

The agent that writes the code should not be the one that decides it works.

Zeroshot turns a software goal into an explicit multi-agent graph. One agent implements. Independent agents review. Failures route back into bounded repair. Delivery happens only after the graph's checks pass.

Zeroshot v8 is a hard interface cutover. The former Node.js runtime is retired; the native zeroshot executable is the product.

Install

npm install -g @the-open-engine-company/zeroshot
zeroshot version

The npm package installs a verified native binary for Linux x64/arm64, macOS x64/arm64, or Windows x64. Native archives and checksums are attached to each canonical vX.Y.Z GitHub Release.

The graph is the orchestration

Agent loops hidden inside prompts are difficult to inspect, reproduce, or trust. Zeroshot makes the control flow authored data: sequence, parallel review, retry paths, delivery, and exit conditions are all explicit before a run starts.

The built-in software-change graph:

1. gives the goal to a worker;
2. runs acceptance and code review independently and in parallel;
3. routes rejected evidence to a repair worker and repeats both reviews;
4. with delivery enabled, delivers an accepted change through Git, CI, and merge;
5. routes delivery conflicts back through repair and review.

No runtime agent chooses the next step. The graph is the orchestration. Every transition is bounded, and every event is written to a durable SQLite ledger.

One authored graph: implement, review, repair when evidence fails, and deliver when it passes.

Inspect the built-ins or bring your own graph:

zeroshot template list
zeroshot template show software-change

One CLI, three environments

The graph and runtime plan stay the same. Only the target changes.

Local — use your subscriptions

Run directly in your Git workspace. Local mode reuses an existing Codex or Claude Code login, including subscription-backed sessions; explicit provider credentials can be bound instead.

zeroshot run \
  --title "Add JSON output with tests" \
  --template software-change \
  --ship \
  --input ./input.json \
  --runtime-config ./runtime.json

Self-hosted — run the Docker target

Keep execution and durable state on infrastructure you control. The target image includes the native engine plus pinned Codex and Claude harness CLIs.

docker run --rm --detach --name zeroshot-target \
  -p 127.0.0.1:8080:8080 \
  -v zeroshot-data:/var/lib/zeroshot/native-v2 \
  ghcr.io/the-open-engine/zeroshot-target:latest

zeroshot target add local --url http://127.0.0.1:8080 --direct

See the target image guide for persistent storage, network isolation, builds, and HTTPS.

Zeroshot Cloud — close the laptop

Use the same CLI against a managed target with a shared team queue and durable run history.

Reference

• CLI reference
• Standalone HTML CLI reference
• Distribution contract
• Target image guide
• Python SDK
• OpenEngine graph contract

Development

npm ci
npm run check
cargo test --workspace

Node.js is repository tooling and the npm delivery mechanism only. See CONTRIBUTING.md, PUBLISHING.md, and SECURITY.md.

License

MIT. See LICENSE.