Bernstein vs Muse: quick decision guide

Install both

curl -fsSL https://dev.meta.ai/install.sh | sh

pipx install bernstein

Feature matrix

Adapter source: src/bernstein/adapters/muse.py | Upstream homepage: dev.meta.ai

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.

1. Bernstein ships a Muse adapter at src/bernstein/adapters/muse.py that wraps the upstream CLI as one of 42 routable agents. [source: bernstein adapter source, as of 2026-08-10]
2. Upstream install command, as recorded in the bernstein adapter, is "curl -fsSL https://dev.meta.ai/install.sh | sh". [source: upstream docs, as of 2026-08-10]
3. 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-08-10]

Where Muse fits in Bernstein

Bernstein registers Muse under the slug "muse" and the registry name "muse". The adapter source lives at src/bernstein/adapters/muse.py in the bernstein repo and was last touched at build time 2026-08-10. The Muse adapter file is 253 lines and 9,958 bytes long, fingerprinted d1c0387f9cb9f789 (first 16 hex chars of SHA-256). Operators install Muse on a worker box with "curl -fsSL https://dev.meta.ai/install.sh | sh" before Bernstein routes any task to it. No upstream GitHub repository is recorded in the bernstein adapter for Muse; refer to the upstream vendor's documentation when auditing. The Muse project's homepage at dev.meta.ai is the primary source for upstream release notes. The bernstein adapter file for Muse does not yet carry a "Last verified against upstream" line; this means the adapter still tracks an unpinned upstream binary. Bernstein routes tasks to Muse 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 Muse adapter, as it stands in the bernstein repo. Punctuation is normalised for the web; the wording is the author's. Length: 1549 characters.

Muse Code CLI adapter for Bernstein. Adapter for Muse Code, Meta's terminal coding agent (https://dev.meta.ai/docs/muse-code). Bernstein drives its documented headless mode - ``muse exec "<prompt>"`` runs a single prompt to completion, intended for scripts and CI - so a Muse Code run gets the same worktree isolation, journaling, and receipts as every other adapter-managed worker. Last verified against vendor docs on 2026-08-10. Install: ``curl -fsSL https://dev.meta.ai/install.sh | sh`` (static binary, macOS/Linux only; no native Windows support). Auth: ``META_API_KEY`` env var for non-interactive environments. Default model: ``muse-spark-1.2``. Version probe: ``muse --version``. Flags used (verified from the vendor configuration/permissions pages): * ``--model <id>`` - common launch flag, passed before the subcommand. * ``--disable-approval`` - skips approval prompts while keeping the CLI's own sandbox containment; required for unattended runs (the interactive approval prompt would hang a headless worker forever). ``--yolo`` also exists but additionally disables the vendor sandbox, which this adapter deliberately does not do. TODO-verify (documented but not consumed yet - re-check at https://dev.meta.ai/docs/muse-code/extending.md before wiring up): * ``--json`` (headless-only JSONL event stream) - unused; the adapter reads plain text output through the standard text-signal channel. * ``--session-id <uuid>`` resumes an existing session non-interactively; resume stays declared unsupported until the resume path supplies one.

Adapter telemetry

When to pick which

FAQ