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