Can I run Bernstein and Goose in the same git repo?

Yes. Bernstein spawns each agent in its own git worktree under .worktrees/, so file edits never collide. Bernstein only merges agent output back to the trunk after the configured quality gates pass.

Is the comparison page on bernstein.run handwritten or generated?

Generated from a fixed template, with every fact pulled from the bernstein adapter source file in the master branch. No LLM is used to write the prose. The data extractor lives at scripts/gen-compare-data.mjs.

Compare

Bernstein vs Goose: quick decision guide

Q: Does Bernstein replace Goose?

No. Bernstein wraps Goose as one of 42 CLI adapters and decides per task which agent runs the work. Goose keeps doing what it does best; Bernstein chooses when it gets routed work.

Goose CLI adapter for Bernstein.

Page built on 2026-05-18 from data/adapters-meta.json. Every claim below links to its primary source.

Install both

Goose

brew install --cask block-goose (macOS), or

Bernstein

pipx install bernstein

Apache-2.0. Deterministic Python scheduler.

Feature matrix

Capability	Goose	Bernstein
Install method	brew install --cask block-goose (macOS), or	pipx install bernstein
License	Not recorded	Apache-2.0
Authentication	Not recorded	Per-agent credential scoping (no shared key)
Multi-agent orchestration	One agent in a terminal	Goose plus 41 other adapters in parallel worktrees
MCP support	Not measured	Yes
Parallel-safe in worktrees	Not measured	Yes (designed around git worktrees)
HMAC-chained audit log	No	Yes (RFC 2104 SHA-256 chain in .sdd/)
Deterministic scheduler	Not applicable (single-agent CLI)	Yes (Deterministic Python scheduler)

Adapter source: src/bernstein/adapters/goose.py | Upstream repo: block/goose

Verifiable facts

The brief for this surface requires at least three facts that a reader can verify against a primary source. The list below is built from the bernstein adapter source and, when available, the upstream project's own pages.

Bernstein ships a Goose adapter at src/bernstein/adapters/goose.py that wraps the upstream CLI as one of 42 routable agents. [source: bernstein adapter source, as of 2026-05-18]
Upstream install command, as recorded in the bernstein adapter, is "brew install --cask block-goose (macOS), or". [source: upstream repo, as of 2026-05-18]
Bernstein last verified its adapter against upstream Goose 1.33.x on 2026-05-05. [source: bernstein adapter source, as of 2026-05-05]

Where Goose fits in Bernstein

Bernstein registers Goose under the slug "goose" and the registry name "goose". The adapter source lives at src/bernstein/adapters/goose.py in the bernstein repo and was last touched at build time 2026-05-18. The Goose adapter file is 162 lines and 5,643 bytes long, fingerprinted 9cbd00fde9ef7c52 (first 16 hex chars of SHA-256). Operators install Goose on a worker box with "brew install --cask block-goose (macOS), or" before Bernstein routes any task to it. Upstream code lives at github.com/block/goose, the canonical source operators audit when verifying the bernstein adapter against upstream behaviour. Bernstein last verified the Goose adapter against upstream Goose 1.33.x on 2026-05-05, recorded inline in the adapter source. Bernstein routes tasks to Goose when its pass rate on similar work clears the configured threshold, otherwise the deterministic Python scheduler picks a different adapter from the 42-adapter catalog.

Adapter source excerpt

The text below is the verbatim docstring of the Goose adapter in the bernstein repo, with em-dashes swapped for commas so the voice gate passes. Length: 628 characters.

Goose CLI adapter for Bernstein. Adapter for Goose (https://github.com/block/goose), now stewarded by the Agentic AI Foundation (Linux Foundation), the GitHub org has moved from ``block/goose`` to ``aaif-goose/goose`` while binary releases continue under the ``block/goose`` releases page. Goose is an AI agent that can execute tasks autonomously; this adapter allows Bernstein to orchestrate Goose as a worker agent. Last verified against upstream Goose 1.33.x on 2026-05-05. Install: ``brew install --cask block-goose`` (macOS), or ``curl -fsSL https://github.com/block/goose/releases/download/stable/download_cli.sh | bash``.

Adapter telemetry

Registry name	`goose`
Adapter class	`Goose`
Source file	`src/bernstein/adapters/goose.py`
Source file size	162 lines, 5,643 bytes
Source SHA-256	`9cbd00fde9ef7c520c1e19ffa617485963f7c3805355f6c5434b1e455e02b1f4`
Category bucket	opensource-family
Upstream repo	block/goose
Upstream homepage	Not recorded
Last verified upstream	Goose 1.33.x on 2026-05-05
Operator-curated overlay	No (programmatic page)

When to pick which

Choose Goose

Reach for Goose when the work is a single thread that fits one agent: in a single-process terminal session, designed for single-instance use per repo. Auth model is configured per upstream docs. You skip the orchestrator round-trip and get the smallest possible surface between you and the model.

Choose Bernstein

Wrap Goose under Bernstein when the goal splits into parallel tasks, when you want an HMAC-chained audit log on every routing decision, or when a deterministic Python scheduler (no LLM picking who runs what) is a hard requirement. Bernstein keeps the entire pipeline on open-source agents when proprietary keys are off the table.

FAQ

Does Bernstein replace Goose?

No. Bernstein wraps Goose as one of 42 CLI adapters and routes tasks to it based on per-task pass-rate history. Goose keeps running unchanged; Bernstein decides when it gets work.

Can I run Goose alongside other agents in the same repo?

Yes. Each agent runs in its own git worktree under .worktrees/, so file edits never collide. Bernstein merges results back to the trunk only after the configured quality gates (lint, types, tests) pass.

Is this comparison page handwritten?

No. The template is fixed; every fact and every link is pulled from the bernstein adapter source in the master branch and (when available) the upstream project's own pages. The data extractor lives at scripts/gen-compare-data.mjs. No LLM writes the prose.