Practical overview
When it fits
Use it for software changes that benefit from separated implementation, verification and controlled repair rather than a single coding-agent pass.
Who it is for
- Developers using coding-agent workflows
- Teams seeking explicit multi-agent software-change orchestration
- Users working with Claude, Codex or Gemini-related environments
Documented uses
- Turn a software goal into an explicit agent graph
- Implement requested repository changes
- Run independent acceptance and code review
- Route failed evidence into bounded repair loops
- Prepare or perform documented delivery flows
Requirements & limits
The project is presented as an accessible public GitHub repository under the MIT license. The documented installation uses npm to install a native binary for Linux, macOS or Windows.
- Whether explicit graph-based orchestration is preferable to hidden prompt loops
- Whether the target workflow needs independent acceptance and code review
- Whether local Git, CI and delivery stages fit the intended process
- Whether the documented Claude, Codex or Gemini-related environment matches the user’s setup
- Whether verifier customization can be supported; repository-specific validation is Likely compatible, while built-in repository-hosting integration Requires modification
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install Zeroshot’s native CLI package
Install the documented Zeroshot executable and its user-scope skills.
Before you start
- npm and a supported target: Linux x64/arm64, macOS x64/arm64, or Windows x64.
Steps
Install the package globally with npm: npm install -g @the-open-engine-company/zeroshot.
Use the installed native Zeroshot executable.
Expected outcome
The package installs a verified native binary and one Zeroshot skill for Codex, GitHub Copilot and Claude Code at user scope.
Guide limitations
- This documents installation only, not a completed software-change run.
- The evidence does not specify npm, provider or account requirements beyond the installation command.
Run a local software-change workflow
Start the documented local CLI flow for a software-change graph.
Before you start
- An existing Git workspace.
- An existing Codex or Claude Code login, or explicit provider credentials.
- A title, input file and runtime configuration file as used in the documented example.
Steps
Run zeroshot run with the software-change template, a title, input file and runtime configuration.
Add --ship when delivery is enabled in the documented example.
Inspect profiles and live or completed runs with zeroshot ui at http://127.0.0.1:4173/ui/.
Expected outcome
The authored graph can move from implementation through independent acceptance and code review, bounded repair when evidence fails, and delivery when enabled.
Guide limitations
- The supplied documentation does not establish that a particular run will succeed.
- The exact runtime configuration format and provider credential setup are not included.
- Delivery and merge behavior depend on the configured workflow.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 30 September 2026
- Original website title
- the-open-engine/zeroshot · Official homepage title · retained in its source language