CerebeCerebe Docs
Cerebe Factory

Review & watch

Run a Cerebe review, follow the factory floor, read the verdict, and address findings without amending.

The workstation critic reviews each commit and gates your push on the result — after you opt in with cerebe model add. cerebe install leaves the local fleet empty; review / gate-push then skip and do not block. The CLI is free to run on any repository. Plans and pricing for the hosted Platform are on the pricing page.

Run a review

A review normally starts on its own from the post-commit hook. To run it directly against the current commit:

cerebe review

The critic reads your repo's rules, reviews the diff, and writes a per-commit verdict, running a multi-vendor quorum from your AI-app subscriptions.

Follow the factory floor

cerebe watch

watch streams each critic's progress and the aggregate verdict as it settles for the current branch.

Read the verdict

cerebe status --commit HEAD   # terse: verdict + per-critic status
cerebe show   --commit HEAD   # full artifact: findings, severities, rationale

Findings are tiered: blocker and high hold your next push; everything below does not block and stays on the record as a dissent.

Push through the gate

git push

With a local fleet enabled, the pre-push gate needs a completed review for the HEAD commit and blocks if that verdict has an open blocker or high finding. It also fails closed when the post-commit review hasn't produced a verdict yet (blockOnMissingReview), so an unreviewed push never slips through — wait for cerebe watch to settle, then push. That fail-close applies only after you have enabled at least one critic. An empty fleet (the cerebe install default) skips the gate; it does not block because no verdict exists. If you're blocked by a finding, fix it in a new commit — never amend. The verdict is bound to the original commit's SHA and diff hash, so an amend detaches the evidence instead of clearing it.

A push blocked by something outside your change can be bypassed. Bypassing the check requires a named, recorded reason, which is saved in the audit trail.

Audit a range

cerebe findings --range origin/main..HEAD   # every finding on the branch
cerebe stats                                # the audit trail, including bypasses

findings reads the recorded findings across a range without re-running the gate.

On this page