bernstein is the open-source governance layer for ai agents: a deterministic python scheduler runs them in parallel, with no model in the coordination loop, so the same plan replays byte-identically. it runs on policy as code: you write the policy, bernstein enforces it, and produces the verifiable record.
ask anything. #
one run, four stages.
decompose
spawn
verify
merge
from the blog
3 pieces, hand-picked. #
field notes from the orchestra pit: what the newest release fixed and what it did not, what running this in the cloud looks like, and how it started.
bernstein 3.14.159: the stranger's ninety minutes #
A first-use report described ninety minutes of setup that ended in nothing. v3.14.159 answers it: the plan raises named errors instead of swallowing malformed fields, five commands are removed and the rest fold with deprecation windows, the reference docs are CI-gated against the registered CLI, and the README says beta. Also new: a Muse Code adapter, Agent Plugins v1.0.0 manifests, a signed run receipt that verifies offline, and bernstein audit diagnose.
agents on cloudflare: workers, durable objects, r2, d1 #
bernstein's cloudflare integration for ai coding agents: workers run agents, workflows carry multi-step tasks, r2 + d1 hold workspace and metering state. experimental; runs on your own account.
bernstein 1.0: open-source orchestrator for ai coding agents #
Orchestrate Claude Code, Codex, Gemini CLI and other CLI coding agents in parallel git worktrees. Deterministic scheduler, HMAC-signed audit chain.
evidence, not vibes
every step signed, in order, on disk. #
run with --audit and bernstein writes an hmac-chained event log under .sdd/audit/, one jsonl file per utc day. each entry references the previous hash. tampering breaks verification. nothing leaves your machine.
someone who did not run it can check it. signature and hash-chain checks read the files alone; the hmac leg needs the key the chain was written with, so hand a reviewer both and bernstein audit verify answers without rerunning anything. not a screenshot, not a SOC2 PDF - a hash chain that recomputes.
configure a signing key and a run also writes an ed25519-signed receipt binding the journal and lineage heads. bernstein verify receipt reads that file alone - no hmac key, no .sdd/. pin the public key for provenance. no key, no receipt.
17:42:01 manager.plan cb84a1… 13 tasks · est $4.20
17:42:18 scheduler.spawn 3e09f7… t-001 → backend (sonnet)
17:42:18 scheduler.spawn 81c2dd… t-002 → backend (sonnet)
17:42:19 scheduler.spawn b50af8… t-003 → qa (opus)
17:55:11 janitor.verify d014a3… t-005 docs · pytest 84/84 · ruff 0
17:55:14 manager.merge ee7c12… t-005 → main · 4 files · clean
18:02:14 janitor.fail 9aa10b… t-003 qa · pytest collect err · 3/3 retries
18:02:30 scheduler.route 71b4cc… t-003 opus → sonnet · awaiting op
18:09:14 scheduler. 4d2e09… conflict · t-001 ↔ t-007 · src/auth/refresh.py
verify chain ok ✓ 412/412 entries · last hash 4d2e09cb…
hmac key ~/.local/state/bernstein/audit.key
frequently asked
the four questions that block install. #
is the scheduler an llm?
does it phone home?
where does it run?
how is this different from claude code?
one engineering post a month.
what we shipped, what broke, what we learned. one click to unsubscribe.