Skip to content

Zeroshot v10.10.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 06 Oct 01:42
v10.10.1
3781f1b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Changes since v10.10.0.

Fixes

Recover immutable README summaries (#1196)

Unblock release-note generation across the two immutable README commits
from PRs #1191 and #1192 that lack a Summary heading. Recover their
summaries through the existing exact-commit table; every other commit
still requires its authored Summary section.

Preserve local USER for macOS Keychain login (#1195)

Preserve the invoking shell's USER in local Claude processes so macOS
Keychain login works without a wrapper. Hosted processes continue to
ignore native context, and explicitly declared connection values take
precedence.

Clarify that safe mode applies only to permission inspection; local
worker and reviewer turns load native Claude customizations.

Documentation

Make the README and llms.txt easy for agents to summarize (#1173)

Agents asked "what can Zeroshot do" read the README and the docs site.
This makes both easier to summarize accurately.

  • README: one-sentence description of the graph instead of four clipped
    sentences, plus "the implementing agent never approves its own work".
  • New "When to use it" section listing fits and non-fits.
  • Opcore pairing in one line: Opcore checks each edit, Zeroshot reviews
    the whole change.
  • Plain wording for PR feedback (--no-pr-feedback) and Cloud merge
    plans; "Not just for coding" becomes "Research graph".
  • New docs/llms.txt, published under current/ by MkDocs and copied
    to the Pages root by the docs workflow.

Checks: npm test (65 pass), Prettier, mkdocs build --strict.

🤖 Generated with Claude Code

Co-authored-by: Eivind eivindcovibes.ai@Eivinds-MacBook-Pro.local
Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

Fix the expired Discord invite and add a Community section (#1174)

The README badge and the docs-site footer linked discord.gg/9Tnxd7XWa,
which Discord reports as expired, so nobody could join from them. Both
now use discord.gg/fZyzf2Cut9, a non-expiring invite to the same
server.

Discord was also only an icon in the badge row. This adds a text link
under the intro, a Community section (Discord, GitHub Discussions,
Issues), and both links in llms.txt so agents can point users there.

Checks: npm test (65 pass), Prettier, mkdocs build --strict.

🤖 Generated with Claude Code

Co-authored-by: Eivind eivindcovibes.ai@Eivinds-MacBook-Pro.local
Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

Make Discord the primary README call to action (#1175)

  • The Discord link was one of four identical dark icons. It is now a
    filled rust Join the Discord button, first in the social row, so it
    reads as the main action in both light and dark themes.
  • The X button image said @OpenEngineCo but linked to
    x.com/OpenEngineHQ. It is re-rendered with the correct handle.
  • Both buttons render from docs/brand/social/buttons.html with the
    bundled Spline Sans. Re-render steps are in docs/brand/README.md. The
    unused discord-*.png icons are removed.

Checks: npm test (65 pass), Prettier, mkdocs build --strict, and a
visual check of the row on GitHub's light and dark backgrounds.

🤖 Generated with Claude Code

Co-authored-by: Eivind eivindcovibes.ai@Eivinds-MacBook-Pro.local
Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

Show the live Discord online count in the README (#1176)

Adds a shields.io Discord badge showing how many members are online,
styled like the other badges (ink label, rust value). The Discord server
widget is now enabled, which the badge needs.

🤖 Generated with Claude Code

Co-authored-by: Eivind eivindcovibes.ai@Eivinds-MacBook-Pro.local
Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

Drop the Discord online-count badge (#1177)

Removes the shields.io Discord online-count badge. The Join the Discord
button in the social row is the single Discord call to action.

🤖 Generated with Claude Code

Co-authored-by: Eivind eivindcovibes.ai@Eivinds-MacBook-Pro.local
Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

Show the companies whose engineers starred zeroshot (#1178)

The README now shows a "Starred by engineers at" strip under the badges:
Google, Meta, Shopify, Uber, Booking.com, GitHub, Cloudflare, Atlassian
and JetBrains. The strip links to the stargazer list. It's the same
proof row that now runs on theopenengine.com and zeroshot.sh.

  • The companies come from the self-reported GitHub company field of
    zeroshot stargazers. I opened each profile before adding it, and the
    copy says "engineers at", never "used by".
  • Source is docs/brand/social/starred-by.html, with Simple Icons marks
    (CC0). It's rendered to transparent light and dark 2× PNGs, the same way
    as the existing README banners. docs/brand/README.md documents the
    source and the render step.

🤖 Generated with Claude Code

Co-authored-by: Eivind eivindcovibes.ai@Eivinds-MacBook-Pro.local
Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

Explain why we built Zeroshot (#1179)

Add the founder's reason for building Zeroshot beneath the README's
independent-review headline: “We built Zeroshot because we were tired of
being gaslit by agents telling us broken code was ready.”

Validation: repository commit and push hooks passed, including Rust
formatting, ESLint and all 65 tooling tests. Opcore pre-commit passed.

Co-authored-by: Eivind Meyer eivind@theopenengine.com

Trim README detail that belongs in the docs (#1180)

The README gets from install to a first run with fewer detours. Detail
for later stays one click away in the docs.

  • Fold the duplicate --validate-only command into one line above the
    run command
  • Move the experimental ACP block, the UI --target note and the resume
    commands to their docs (resume keeps a link)
  • Drop the checksums line and the HTML CLI, distribution contract and
    ACP Reference links

Claims and links checked against main.

🤖 Generated with Claude Code

Co-authored-by: Eivind eivindcovibes.ai@Eivinds-MacBook-Pro.local
Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

Show a single agent vs Zeroshot run in the README (#1182)

The README now shows a scripted side-by-side run under the intro: one
agent checking its own work next to Zeroshot on the same invoice CSV
export task. The thumbnail is the run's final frame and links to the
full video on X.

  • docs/assets/zeroshot-vs-single-agent.png: final frame, 1280px wide
  • Caption states the scenario is scripted, not a benchmark

🤖 Generated with Claude Code

Co-authored-by: Eivind eivindcovibes.ai@Eivinds-MacBook-Pro.local
Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

Link the comparison video instead of embedding a thumbnail (#1183)

The README now links the single agent vs. Zeroshot video on X with one
line instead of embedding a thumbnail, which was hard to read at README
width. The unused thumbnail asset is removed.

🤖 Generated with Claude Code

Co-authored-by: Eivind eivindcovibes.ai@Eivinds-MacBook-Pro.local
Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

Tighten the README intro and community links (#1184)

The README goes from the intro and video link straight to Install. The
"When to use it" section is removed, the v8 cutover notice moves under
Install, the Opcore paragraph moves to its own short section before
Community, and GitHub Discussions is dropped from the community links.

🤖 Generated with Claude Code

Co-authored-by: Eivind eivindcovibes.ai@Eivinds-MacBook-Pro.local
Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

Move Opcore link to README references (#1185)

Replace the README’s “Works with Opcore” section with a short reference
link. Add “Also check out:
Opcore.” beneath the
existing Reference list.

Link zeroshot.sh from the README, npm package, and docs site (#1186)

Point GitHub, npm, and docs visitors at the product site, zeroshot.sh.

  • README: the "Website" button now links to zeroshot.sh (new
    zeroshot-site light/dark button rendered from
    docs/brand/social/buttons.html); the theopenengine.com button stays as
    the company link. One text line under the intro names zeroshot.sh. Both
    sites carry
    ?utm_source=github&utm_medium=readme&utm_campaign=zeroshot. Docs badge
    unchanged.
  • npm package: homepage is now https://zeroshot.sh (no UTM, npm
    shows it raw); the npm README gets one zeroshot.sh line tagged
    utm_source=npm&utm_medium=readme.
  • Docs site: a zeroshot.sh entry at the end of the nav and a globe icon
    in the footer social links, tagged utm_source=github&utm_medium=docs.

Link the Zeroshot Cloud docs and stop pointing at dev (#1187)

The docs now link to the Zeroshot Cloud documentation at
https://cloud.zeroshot.sh/docs. Before this change, the docs home page
and the Targets page sent readers to dev.theopenengine.com/docs, the
zero-cloud dev environment.

  • docs/index.md, docs/concepts/targets.md: replace the dev URL with
    https://cloud.zeroshot.sh/docs
  • README: link the Cloud docs from the "Zeroshot Cloud: close the
    laptop" section and add them to the Reference list
  • mkdocs.yml: add a "Zeroshot Cloud" nav entry
  • docs/llms.txt: add the Cloud docs to the Docs list
  • zeroshot target --help: point to the Cloud docs (CLI reference
    regenerated with generate_cli_docs --write)

Published minor versions keep the dev link until their next patch
rebuild.

Add RuntimePlan reference and review-loop guide (#1188)

  • New RuntimePlan reference (docs/reference/runtime-plan.md):
    document fields, harness/provider grammar, agent and git_delivery
    bindings (including which delivery workers accept pullRequestFeedback: ignore), session-scope semantics, coverage rules, connection limits,
    uniform runtime expansion, and how --push/--pr/--ship add
    template-owned delivery bindings (and the agent nodes an exact plan must
    then bind, such as delivery_repair). Links the generated schema.json
    as the machine-readable contract.
  • New Build a review loop guide (docs/guides/review-loop.md): a
    worker plus two parallel reviewers in a bounded loop, local by default,
    with a one-line note on targets. The complete graph, runtime plan, and
    input ship as downloadable files under docs/assets/review-loop/ and
    are included into the page with pymdownx.snippets, so the page shows
    exactly the validated files.
  • Direct target (docs/concepts/targets.md): new "Image tags and
    remote hosts" subsection: linux/amd64 only, version/sha- tags vs
    moving latest, SSH tunnel to a loopback-published target, no caller
    authentication, link to the target image README for proxies.
  • Both new pages are in the nav (RuntimePlan under Reference > Cluster
    protocol) and llms.txt, and the docs manifest gains logical routes
    runtimePlanReference and reviewLoop. The docs hook now omits any
    route whose page is absent from the built site, so republishing an older
    release with the current hook keeps working; versioning.md tells
    clients to treat a missing route key as not documented in that version.
  • The harness/provider table and session-scope detail now live only in
    the reference; the concept pages link to it. The runtimes concept page,
    execution concept page, and graph contract link to the new pages.

This gives Zeroshot Cloud's docs a versioned core page to link to
instead of keeping their own copies.

Show per-step models and mark the custom topology as an example (#1190)

Three README changes from reader feedback:

  • The built-in workflow now says the repair worker gets both reviews'
    feedback, which explains why the reviews run in parallel.
  • The bugfinder/E2E topology is labelled as an illustration of a custom
    graph, not something Zeroshot ships.
  • "Save and reuse a profile" shows a --runtime-config plan with a
    model per node and links the RuntimePlan reference.

Checked the example plan with zeroshot run --template software-change --runtime-config … --validate-only ({"valid":true}).

🤖 Generated with Claude Code

Co-authored-by: Eivind eivindcovibes.ai@Eivinds-MacBook-Pro.local
Co-authored-by: Claude Opus 5.5 noreply@anthropic.com

Say Zeroshot runs the user's existing coding agent (#1191)

Clarify that Zeroshot runs the user's existing coding agent as workers and reviewers.

Label the custom topology as an example (#1192)

Clarify that the README's custom bugfinder/E2E topology is an example and only the review loop is built in.

Upgrade

npm install -g @the-open-engine-company/zeroshot@10.10.1
Assets 10
Loading