The GitHub App

The Platform is the hosted half of Cerebe: the GitHub App runs an independent panel on every pull request and posts one verdict as the cerebe/critic check. It is the authority the workstation CLI defers to. Plans and pricing are on the pricing page.

Install the App

Install the Cerebe GitHub App on a repository or an organization. Once it's installed, every pull request runs the panel automatically — no workflow YAML to add, and no model keys to store in your CI.

Sign in at factory.cerebe.ai for the dashboard across your repositories.

Require the check

The App posts its verdict on every pull request as one check, named cerebe/critic. On a paid plan, when cerebe/critic is a required status check, a pull request merges only on an approving verdict, and a missing verdict blocks. Without a paid plan, or until the check is required, the verdict is posted and does not block.

To require the check, add cerebe/critic to the repository's required status checks, with a ruleset or with a branch protection rule.

With a ruleset:

1. On GitHub, open the repository's Settings, then Rules, then Rulesets.
2. Select New ruleset, then New branch ruleset, or open the ruleset that already covers the branch.
3. Name it, set Enforcement status to Active, and under Target branches add the branch you merge into.
4. Turn on Require status checks to pass, select Add checks, and search for cerebe/critic.
5. Select the cerebe/critic entry posted by the Cerebe GitHub App (GitHub lists the App as Cerebe Factory), then save the ruleset.

With a branch protection rule:

1. On GitHub, open the repository's Settings, then Branches.
2. Select Add classic branch protection rule, or Edit on the rule for the branch you merge into.
3. Turn on Require status checks to pass before merging and search for cerebe/critic.
4. Select it, choose the Cerebe GitHub App (Cerebe Factory) as its source, and save the rule.

If cerebe/critic is not in the search results, open or update a pull request so the App posts the check, then search again.

What the panel does

Independent critics from rival model families review the change in parallel, each on its own, and a deterministic kernel turns their findings into one verdict — the same kernel that runs on your workstation. The workstation critic is a convenience that shares this kernel; the hosted App runs its own independent critic fleet and remains the authority that gates merge. On the Platform, blocking takes corroboration: a blocking finding holds the merge when a second independent critic reports it at the same place, and a finding that stands alone is kept on the record as a dissent.

Every verdict is bound to the commit SHA and its diff — amend the commit and the panel re-runs, and a stale diff is rejected rather than judged. Overriding the check takes a named person and a recorded reason.