Can I run Bernstein and Forge 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 Forge: quick decision guide

Q: Does Bernstein replace Forge?

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

Forge CLI adapter.

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

Install both

Forge

curl -fsSL https://forgecode.dev/cli | sh

Bernstein

pipx install bernstein

Apache-2.0. Deterministic Python scheduler.

Feature matrix

Capability	Forge	Bernstein
Install method	curl -fsSL https://forgecode.dev/cli \| sh	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	Forge 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/forge.py | Upstream homepage: forgecode.dev

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 Forge adapter at src/bernstein/adapters/forge.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 "curl -fsSL https://forgecode.dev/cli | sh". [source: upstream docs, as of 2026-05-18]
Bernstein is an open-source Multi-agent orchestrator licensed Apache-2.0, with a deterministic Python scheduler that routes work across CLI agents in parallel git worktrees. [source: bernstein repo, as of 2026-05-18]

Where Forge fits in Bernstein

Bernstein registers Forge under the slug "forge" and the registry name "forge". The adapter source lives at src/bernstein/adapters/forge.py in the bernstein repo and was last touched at build time 2026-05-18. The Forge adapter file is 108 lines and 3,934 bytes long, fingerprinted eed3bcce88f3e302 (first 16 hex chars of SHA-256). Operators install Forge on a worker box with "curl -fsSL https://forgecode.dev/cli | sh" before Bernstein routes any task to it. No upstream GitHub repository is recorded in the bernstein adapter for Forge; refer to the upstream vendor's documentation when auditing. The Forge project's homepage at forgecode.dev is the primary source for upstream release notes. The bernstein adapter file for Forge does not yet carry a "Last verified against upstream" line; this means the adapter still tracks an unpinned upstream binary. Bernstein routes tasks to Forge 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 Forge adapter in the bernstein repo, with em-dashes swapped for commas so the voice gate passes. Length: 18 characters.

Forge CLI adapter.

Adapter telemetry

Registry name	`forge`
Adapter class	`Forge`
Source file	`src/bernstein/adapters/forge.py`
Source file size	108 lines, 3,934 bytes
Source SHA-256	`eed3bcce88f3e302ba7c16fa75492cc5ce15833a9f9a753d269ee173d5ba8565`
Category bucket	cli-family
Upstream repo	Not derivable from adapter source
Upstream homepage	forgecode.dev
Last verified upstream	No "Last verified" line in adapter source
Operator-curated overlay	No (programmatic page)

When to pick which

Choose Forge

Reach for Forge 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 Forge 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.

FAQ

Does Bernstein replace Forge?

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

Can I run Forge 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.