All stories
Zeroshot Ecosystem Community reports

Zeroshot lets coding agents work in folders without Git

Version 10.12.0 removes the Git prerequisite for local, no-delivery runs while keeping separate implementation and review agents. Docker, cloud and delivery still have stricter source requirements.

By AITrending2 min read
Sources (2)

Why now The English v10.12.0 release was published October 15 at 13:31:24 UTC. Its release notes explicitly add --cwd and non-Git local folders; a repository observation time is not being presented as the release date.
Zeroshot's illustrated workflow with implementation, independent parallel acceptance and code reviews, repair loops and optional Git delivery.
First frame of the project's versioned workflow animation, resized without cropping. This is an author illustration of the built-in workflow, not an AITrending execution or proof of correctness. Source: The Open Engine Company / Zeroshot

Bring the folder, skip the repository setup

Zeroshot 10.12.0 gives its coding-agent workflow a simpler starting point: a local folder. The October 15 release adds --cwd and support for folders without Git, so a local run that does not request delivery can work without first creating a repository.

This is a standalone orchestration harness, rather than a new model or a fork of a coding assistant. It runs installed Claude Code, Codex or GitHub Copilot harnesses as workers and reviewers. The model provider is a separate choice and can differ between agents.

The project’s built-in software-change workflow sends a task through implementation, then independent acceptance and code reviews in parallel. If either review fails, the workflow can repair the work and return it to both reviewers, within configured retry bounds. The engine prevents a worker from approving its own work. These are the project’s documented execution rules; AITrending has not run the workflow or established that a passing result is universally correct.

Local edits and delivery are different permissions

The selected local folder is edited directly. Removing the Git requirement does not turn local execution into a sandbox or give it automatic rollback. --cwd chooses the target folder, while input-file paths remain relative to the invoking folder. The documented --validate-only option checks graph, runtime and inputs before execution.

Git is still part of other paths. Docker and cloud runs retain exact Git provenance. Push delivery needs a committed checkout and an HTTPS or SSH remote; pull-request and shipping modes also need a forge adapter, with GitHub the maintained provider today. A local run without a delivery flag stays local. --pr prepares a pull request without merging, while --ship includes the PR, CI and merge path.

Installation uses an existing coding harness

The release’s upgrade command is npm install -g @the-open-engine-company/zeroshot@10.12.0. The README requires Node.js 18 or newer and lists native binaries for Linux and macOS on x64 and arm64, plus Windows x64. Installation also places a Zeroshot skill at user scope for the supported coding harnesses.

Users still need a supported harness installed and signed in; local execution can reuse its existing subscription-backed login. The CLI is described as MIT-licensed, but model usage and cloud service costs are separate. The change is a more accessible local workflow, with review gates and optional delivery, rather than a promise of free or unattended correctness.

Related reading