sipyourdrink-ltd

bernstein: Govern and Audit AI Agent Workflows

Bernstein is a Python governance layer for AI agents, using a deterministic scheduler to run and gate workflows under declarative policies. It records verifiable run history for offline replay, covering coding tasks and other deliverables.

ActivePythonApache-2.0AI AgentsCLIAgent Orchestration
Stars
1.2k
Forks
186
Stars, last 30 days
-41
Last commit
today
Contributors
100+

Our take

Activeregular commits and releases

Health score

78/100

How it is scored
Activity
90
Community
68
Issues
76
Pull requests
78

-41 stars in the last 30 days

  • Releases more often than 93% of the projects we track
  • Merges more pull requests than 84% of the projects we track
  • More contributors than 77% of the projects we track

Bernstein is a capable fit for teams that need governed, inspectable agent workflows, with active development and broad recent project activity, but its beta status and evolving interfaces call for version pinning.

Good fit if

  • You want explicit policy, role, and approval controls around parallel agent work.
  • Offline verification and local or air-gapped operation matter to your workflow.
  • Your team can run Python 3.12 or newer and is comfortable adopting a beta project under Apache-2.0.

Look elsewhere if

  • You need a stable interface with a long maturity track record, since the project explicitly warns that minor versions may change interfaces.
  • You require the hosted cloud execution service described in the docs, which the README says is not yet available.
  • You want a turnkey volunteer task runner, since its autopilot command is registered but not usable until a task source is implemented.
All health signals
Last commit2026-11-08 (today)
Commits, last 90 days100+
Releases, last 12 months100+ (latest v3.24.1, 2026-11-05)
Contributors100+ (top contributor: 73% of commits)
Issues closed, last 90 days15+ (typically closed in 1 day)
Pull requests merged, last 90 days76 (typically merged in 0 days)
Project age8 months

Checked on 2026-11-09 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

1,206

Forks

186

Change since Nov 13, 2026: +1 stars·+2 forks

Overview

Bernstein is a Python governance and orchestration layer for AI agents, built around a deterministic scheduler written in plain Python rather than an LLM coordination loop. Teams declare workflow rules, roles, dependencies, and approval conditions; Bernstein schedules agent work, applies gates, and records evidence that can be checked after a run.

It targets teams that need parallel agent work without giving up control over how tasks are assigned, verified, and recorded. It supports CLI coding agents such as Claude Code, Codex, and Gemini CLI, as well as other agent workloads that produce reports, datasets, or operational evidence. Runs use local files and can be installed for air-gapped environments.

Key Features

  • Declarative YAML workflows describe phases, roles, dependencies, conditional execution, and retries.
  • Deterministic scheduling runs in Python, with no model deciding the coordination sequence.
  • Coding tasks can run in separate Git worktrees and pass merge gates; artifact tasks can finish against a declared contract and signed lineage receipt.
  • Replay journals and lineage records support verification after execution; optional audit logging adds an HMAC chain.
  • Signed run receipts support offline checks, with the README noting that identity verification requires a pinned public key.
  • CLI, terminal, and browser operator surfaces expose task status, and the project lists 54 selectable agent adapters.
  • Air-gap installation and local file-based state are available for environments avoiding a hosted data plane.

Use Cases

  • A development team can split coding work across agents while keeping tasks isolated and requiring tests or other signals before merging.
  • A security or compliance team can assemble evidence from logs, policies, scans, and evaluations, then retain verifiable run records.
  • A research or operations group can coordinate agent tasks whose outputs are reports, datasets, or action logs rather than code changes.
  • Teams evaluating agent reliability can run tasks repeatedly and verify the resulting reliability receipt offline.

What you need

Detected in the repository

  • Python >=3.12 (from pyproject.toml)
  • A Dockerfile, so it can run in a container; a Compose file sets up the related services
  • A test suite and automated checks on GitHub Actions

License in plain words

Apache-2.0permissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the license, the NOTICE file and a note of your changes
  • Share your changes: no
  • Includes an explicit patent grant from the contributors:

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Install with uv tool install bernstein, then run bernstein init and bernstein doctor to check your setup. See the README and installation guide for details.

Alternatives

  • agent-governance-toolkit: It governs agents through identity, sandboxing, and policy controls across frameworks, rather than Bernstein’s deterministic workflow scheduling and replay.
  • intent-plane: It focuses on fail-closed authorization for irreversible actions using signed policies, rather than governing and replaying complete agent workflows.
ProjectLanguageLicenseStarsStatus
bernsteinPythonApache-2.01.2kActive
agent-governance-toolkitPythonMIT6.6kActive
intent-planeGo–1New

Considerations

The README labels Bernstein beta, says it is solo-maintained, and warns that minor releases can change interfaces. Repository activity is recent and ongoing, and the measured contributor base is not concentrated around one person; issue and pull request handling has also been active. Even so, teams should pin versions and test upgrades against their workflows. Python 3.12 or newer is required; Docker is also supported. The README identifies incomplete volunteer autopilot and unavailable hosted cloud execution as limitations. Apache-2.0 applies to the code, while the project name is covered separately by its trademark policy.

Found this useful?

Share it with someone who would like bernstein.

Comparisons