Zeroshot v8 CLI Adopts Native Executable, Retires Node.js Runtime

What changed

Zeroshot has introduced version 8 of its autonomous engineering team CLI, marking a significant architectural change with the retirement of its former Node.js runtime in favor of a native zeroshot executable. This hard interface cutover means that users will now install and interact with a compiled binary, rather than a Node.js-based package.

The installation process has been updated to use npm install -g @the-open-engine-company/zeroshot, which now installs a verified native binary for Linux (x64/arm64), macOS (x64/arm64), and Windows (x64). Alongside the binary, the npm package also installs one Zeroshot skill for Codex, GitHub Copilot, and Claude Code at the user scope. Native archives and checksums are provided with each vX.Y.Z GitHub Release.

Zeroshot's core functionality revolves around an agent loop that produces code through a multi-agent graph. This graph explicitly defines the control flow, including sequence, parallel review, retry paths, delivery, and exit conditions, before a run commences. The built-in software-change graph orchestrates tasks such as assigning goals to a worker, running acceptance and code reviews in parallel, routing rejections for repair, and delivering accepted changes via Git, CI, and merge. Failures are managed through bounded repair loops, and delivery only proceeds after the graph's checks are satisfied. All transitions are bounded, and events are recorded in a durable SQLite ledger.

Developers can inspect built-in graphs or create their own using zeroshot template list and zeroshot template show. The auto-research graph, for example, runs multiple bounded iterations with scout, synthesizer, and challenger agents, reviewed by evidence, method, and progress judges. The graph maintains its charter, summary, backlog, state, iteration records, and reversible backups under .zeroshot/research.

The CLI supports three execution environments: Local, Self-hosted, and Zeroshot Cloud. Local mode allows direct use within a Git workspace, reusing existing Codex or Claude Code logins or binding explicit provider credentials. The zeroshot run command can be used with options like --title, --template, --ship, --input, and --runtime-config. A zeroshot ui command is available for editing profiles and inspecting runs in a browser.

Self-hosted execution utilizes a Docker target image (ghcr.io/the-open-engine/zeroshot-target:latest) that includes the native engine and harness CLIs for Codex, Claude, and GitHub Copilot. This allows for execution and state management on user-controlled infrastructure. The target image also exposes its own UI at http://127.0.0.1:8080/ui/.

Zeroshot Cloud offers a shared team queue and durable run history via the cloud target at https://api.cloud.zeroshot.sh. Users can log in using zeroshot target login cloud. Failed runs with recoverable workspaces can be resumed using zeroshot resume RUN_ID, with options to restart on the latest files or from an earlier checkpoint.

Why it matters for builders

The transition to a native executable in Zeroshot v8 simplifies the developer experience by removing Node.js as a dependency for the CLI itself. This means easier installation and potentially faster startup times for the autonomous engineering tool. Builders can now integrate Zeroshot more seamlessly into their development pipelines, relying on a more robust and performant command-line interface for generating and reviewing code.

Practical impact

Developers looking to use Zeroshot should update to version 8 via npm install -g @the-open-engine-company/zeroshot. After updating, they can leverage the native executable for all Zeroshot commands. It is recommended to review the installation instructions for their specific operating system (Linux, macOS, Windows) and to explore the updated documentation for managing graphs and utilizing the different execution targets (Local, Self-hosted Docker, Zeroshot Cloud).

Caveats and source limits

The source material indicates that Zeroshot v8 represents a "hard interface cutover," meaning the previous Node.js runtime is retired. Users must update to the new native executable. Specific performance benchmarks comparing the Node.js runtime to the new native executable are not provided in the source. The exact details of the "trivial setup" for supporting various AI models like Claude Code, OpenAI Codex, and Gemini CLI are not elaborated upon beyond the installation command.