zeroshot CLI

🎉 New in v5.4: Now supports OpenCode CLI! Use Claude, Codex, Gemini, or OpenCode as your AI provider. Also supports GitHub, GitLab, Jira, and Azure DevOps as issue backends. See Providers and Multi-Platform Issue Support.

Zeroshot is an open-source AI coding agent orchestration CLI that runs multi-agent workflows to autonomously implement, review, test, and verify code changes.

It runs a planner, an implementer, and independent validators in isolated environments, looping until changes are verified or rejected with actionable, reproducible failures.

Built for tasks where correctness matters more than speed.

How It Works

• Plan: translate a task into concrete acceptance criteria
• Implement: make changes in an isolated workspace (local, worktree, or Docker)
• Validate: run automated checks with independent validators
• Iterate: repeat until verified, or return actionable failures
• Resume: crash-safe state persisted for recovery

Quick Start

zeroshot run 123                    # GitHub issue number
zeroshot run feature.md             # Markdown file
zeroshot run "Add dark mode"        # Inline text

Or describe a complex task inline:

zeroshot run "Add optimistic locking with automatic retry: when updating a user,
retry with exponential backoff up to 3 times, merge non-conflicting field changes,
and surface conflicts with details. Handle the ABA problem where version goes A->B->A."

Why Not Just Use a Single AI Agent?

Use Cases

• Autonomous AI code refactoring
• AI-powered pull request automation
• Automated bug fixing with validation
• Multi-agent code generation for software engineering
• Agentic coding workflows with blind validation

Who Is This For?

• Senior engineers who care about correctness and reproducibility
• Teams automating PR workflows and code review gates
• Infra/platform teams standardizing agentic workflows
• Open-source maintainers working through issue backlogs
• AI power users who want verification, not vibes

Install and Requirements

Platforms: Linux, macOS. Windows (native/WSL) is deferred while we harden reliability and multi-provider correctness.

npm install -g @covibes/zeroshot

Requires: Node 18+, at least one provider CLI (Claude Code, Codex, Gemini, Opencode).

# Install one or more providers
npm i -g @anthropic-ai/claude-code
npm i -g @openai/codex
npm i -g @google/gemini-cli
# Opencode: see https://opencode.ai

# Authenticate with the provider CLI
claude login        # Claude
codex login         # Codex
gemini auth login   # Gemini
opencode auth login # Opencode

# GitHub auth (for issue numbers)
gh auth login

Providers

Zeroshot shells out to provider CLIs. Pick a default and override per run:

zeroshot providers
zeroshot providers set-default codex
zeroshot run 123 --provider gemini

See docs/providers.md for setup, model levels, and Docker mounts. See docs/provider-cli-helper.md for the strict TypeScript provider helper, the zeroshot-agent-provider JSON executable contract, and the boundary with Orchestra.

Why Multiple Agents?

Single-agent sessions degrade. Context gets buried under thousands of tokens. The model optimizes for "done" over "correct."

Zeroshot fixes this with isolated agents that check each other's work. Validators can't lie about code they didn't write. Fail the check? Fix and retry until it actually works.

What Makes It Different

• Blind validation - Validators never see the worker's context or code history
• Repeatable workflows - Task complexity determines agent count and model selection
• Accept/reject loop - Rejections include actionable findings, not vague complaints
• Crash recovery - All state persisted to SQLite; resume anytime
• Isolation modes - None, git worktree, or Docker container
• Cost control - Model ceilings prevent runaway API spend

Required Handoff Quality Gates

Zeroshot owns a tool-neutral handoff contract for --pr and --ship flows. It does not know which tool produced a gate. Repos configure required gates, validators publish matching qualityGates evidence, and the git-pusher trigger refuses to wake until every configured gate has fresh passing evidence after IMPLEMENTATION_READY.

Gate config can come from run options or repo settings:

{
  "ship": {
    "requiredQualityGates": [
      {
        "id": "repo-quality",
        "scope": "repo",
        "description": "Repository quality gate",
        "command": "repo-quality --changed --json"
      }
    ]
  }
}

The id and optional scope are generic. A repo may bind repo-quality to any local quality command, a CI status command, or another quality command outside Zeroshot. Validators receive the configured gate list and must publish entries with status, completedAt or timestamp, and evidence.command, evidence.exitCode, and string evidence.output. Failing or unavailable commands mean approved: false with gate status FAIL or UNAVAILABLE.

The pusher fails closed before commit, push, PR creation, or merge when a configured gate is missing, failing, unavailable, stale, older than IMPLEMENTATION_READY, or lacks usable evidence. If no requiredQualityGates are configured, Zeroshot preserves its existing validator consensus behavior.

When to Use Zeroshot

Zeroshot performs best when tasks have clear acceptance criteria.

Rule of thumb: if you cannot describe what "done" means, validators cannot verify it.

Command Overview

# Run
zeroshot run 123                      # GitHub issue
zeroshot run feature.md               # Markdown file
zeroshot run "Add dark mode"          # Inline text

# Isolation
zeroshot run 123 --worktree       # git worktree
zeroshot run 123 --docker         # container

# Automation (--ship implies --pr implies --worktree)
zeroshot run 123 --pr             # worktree + create PR
zeroshot run 123 --ship           # PR + auto-merge on approval

# Background mode
zeroshot run 123 -d
zeroshot run 123 --ship -d

# Control
zeroshot list
zeroshot status <id>
zeroshot logs <id> -f
zeroshot resume <id>
zeroshot stop <id>
zeroshot kill <id>

# Providers
zeroshot providers
zeroshot providers set-default codex

# Agent library
zeroshot agents list
zeroshot agents show <name>

# Maintenance
zeroshot clean
zeroshot purge

Multi-Platform Issue Support

Zeroshot works with GitHub, GitLab, Jira, and Azure DevOps. Just paste the issue URL or key. When working in a git repository, zeroshot automatically detects the issue provider from your git remote URL. No configuration needed!

# GitHub
zeroshot run 123
zeroshot run https://github.com/org/repo/issues/123

# GitLab (cloud and self-hosted)
zeroshot run https://gitlab.com/org/repo/-/issues/456
zeroshot run https://gitlab.mycompany.com/org/repo/-/issues/789

# Jira
zeroshot run PROJ-789
zeroshot run https://company.atlassian.net/browse/PROJ-789

# Azure DevOps
zeroshot run https://dev.azure.com/org/project/_workitems/edit/999

Requires: CLI tools (gh, glab, jira, or az) for the platform you use. See issue-providers README for setup and self-hosted instances.

Important for --pr mode: Run zeroshot from the target repository directory. PRs are created on the git remote of your current directory. If you run from a different repo, zeroshot will warn you and skip the "Closes #X" reference (the PR is still created, but won't auto-close the issue