Compare
Bernstein vs Continue.dev: quick decision guide
Continue.dev CLI adapter.
Page built on 2026-08-16 from data/adapters-meta.json. Every claim below links to its primary source.
Install both
Continue.dev
npm install -g @continuedev/cli (binary is cn)Bernstein
pipx install bernsteinApache-2.0. Deterministic Python scheduler.
Feature matrix
| Capability | Continue.dev | Bernstein |
|---|---|---|
| Install method | npm install -g @continuedev/cli (binary is cn) | 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 | Continue.dev plus 40+ 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/continue_dev.py | Upstream homepage: www.continue.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 Continue.dev adapter at src/bernstein/adapters/continue_dev.py that wraps the upstream CLI as one of 42 routable agents. [source: bernstein adapter source, as of 2026-08-16]
- Upstream install command, as recorded in the bernstein adapter, is "npm install -g @continuedev/cli (binary is cn)". [source: upstream docs, as of 2026-08-16]
- Bernstein last verified its adapter against upstream @continuedev/cli 1.5.47 on 2026-08-10. [source: bernstein adapter source, as of 2026-08-10]
Where Continue.dev fits in Bernstein
Bernstein registers Continue.dev under the slug "continue" and the registry name "continue". The adapter source lives at src/bernstein/adapters/continue_dev.py in the bernstein repo and was last touched at build time 2026-08-16. The Continue.dev adapter file is 143 lines and 5,170 bytes long, fingerprinted e39154212170f9ae (first 16 hex chars of SHA-256). Operators install Continue.dev on a worker box with "npm install -g @continuedev/cli (binary is cn)" before Bernstein routes any task to it. No upstream GitHub repository is recorded in the bernstein adapter for Continue.dev; refer to the upstream vendor's documentation when auditing. The Continue.dev project's homepage at www.continue.dev is the primary source for upstream release notes. Bernstein last verified the Continue.dev adapter against upstream @continuedev/cli 1.5.47 on 2026-08-10, recorded inline in the adapter source. Bernstein routes tasks to Continue.dev when its pass rate on similar work clears the configured threshold, otherwise the deterministic Python scheduler picks a different adapter from the 40+ adapter catalog.
Adapter source excerpt
The module docstring of the Continue.dev adapter, as it stands in the bernstein repo. Punctuation is normalised for the web; the wording is the author's. Length: 743 characters.
Continue.dev CLI adapter. Continue (https://www.continue.dev/) is an open-source AI coding assistant for VS Code and JetBrains. This adapter invokes the Continue CLI (``cn``) in headless mode for non-interactive task execution. Installation: ``npm install -g @continuedev/cli`` (binary is ``cn``). Authentication: ``~/.continue/config.yaml`` or provider API keys in the env. Model selection is driven by the Continue config, so ``model_config.model`` is logged only. Note: ``cn`` 1.5.x does expose a ``--model`` flag, but it takes a Continue *hub slug* (``owner/package``) rather than a provider model ID, so Bernstein's model identifiers cannot be passed through unmapped. Last verified against upstream @continuedev/cli 1.5.47 on 2026-08-10.Adapter telemetry
| Registry name | continue |
|---|---|
| Adapter class | Continue.dev |
| Source file | src/bernstein/adapters/continue_dev.py |
| Source file size | 143 lines, 5,170 bytes |
| Source SHA-256 | e39154212170f9ae92442130f46ba29549d7f552c415b7d43b060359ef20ae8f |
| Category bucket | opensource-family |
| Upstream repo | Not derivable from adapter source |
| Upstream homepage | www.continue.dev |
| Last verified upstream | @continuedev/cli 1.5.47 on 2026-08-10 |
| Operator-curated overlay | No (programmatic page) |
When to pick which
Choose Continue.dev
Reach for Continue.dev 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 Continue.dev 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 Continue.dev?
No. Bernstein wraps Continue.dev as one of 40+ CLI adapters and routes tasks to it based on per-task pass-rate history. Continue.dev keeps running unchanged; Bernstein decides when it gets work.
Can I run Continue.dev alongside other agents in the same repo?
Yes. Each agent runs in its own git worktree under .sdd/worktrees/{session_id}, 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.