Compare
Bernstein vs Auggie (Augment Code): quick decision guide
Auggie (Augment Code) CLI adapter.
Page built on 2026-05-18 from data/adapters-meta.json. Every claim below links to its primary source.
Install both
Auggie (Augment Code)
npm install -g @augmentcode/auggieBernstein
pipx install bernsteinApache-2.0. Deterministic Python scheduler.
Feature matrix
| Capability | Auggie (Augment Code) | Bernstein |
|---|---|---|
| Install method | npm install -g @augmentcode/auggie | 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 | Auggie (Augment Code) 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/auggie.py | Upstream homepage: docs.augmentcode.com
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 Auggie (Augment Code) adapter at src/bernstein/adapters/auggie.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 "npm install -g @augmentcode/auggie". [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 Auggie (Augment Code) fits in Bernstein
Bernstein registers Auggie (Augment Code) under the slug "auggie" and the registry name "auggie". The adapter source lives at src/bernstein/adapters/auggie.py in the bernstein repo and was last touched at build time 2026-05-18. The Auggie (Augment Code) adapter file is 111 lines and 4,171 bytes long, fingerprinted b236d51e679939c6 (first 16 hex chars of SHA-256). Operators install Auggie (Augment Code) on a worker box with "npm install -g @augmentcode/auggie" before Bernstein routes any task to it. No upstream GitHub repository is recorded in the bernstein adapter for Auggie (Augment Code); refer to the upstream vendor's documentation when auditing. The Auggie (Augment Code) project's homepage at docs.augmentcode.com is the primary source for upstream release notes. The bernstein adapter file for Auggie (Augment Code) does not yet carry a "Last verified against upstream" line; this means the adapter still tracks an unpinned upstream binary. Bernstein routes tasks to Auggie (Augment Code) 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 Auggie (Augment Code) adapter in the bernstein repo, with em-dashes swapped for commas so the voice gate passes. Length: 34 characters.
Auggie (Augment Code) CLI adapter.Adapter telemetry
| Registry name | auggie |
|---|---|
| Adapter class | Auggie (Augment Code) |
| Source file | src/bernstein/adapters/auggie.py |
| Source file size | 111 lines, 4,171 bytes |
| Source SHA-256 | b236d51e679939c604d3a63f5d78811cfbe57d2e35155f27d40eb2789dbaf6b1 |
| Category bucket | cli-family |
| Upstream repo | Not derivable from adapter source |
| Upstream homepage | docs.augmentcode.com |
| Last verified upstream | No "Last verified" line in adapter source |
| Operator-curated overlay | No (programmatic page) |
When to pick which
Choose Auggie (Augment Code)
Reach for Auggie (Augment Code) 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 Auggie (Augment Code) 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 Auggie (Augment Code)?
No. Bernstein wraps Auggie (Augment Code) as one of 42 CLI adapters and routes tasks to it based on per-task pass-rate history. Auggie (Augment Code) keeps running unchanged; Bernstein decides when it gets work.
Can I run Auggie (Augment Code) 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.