critiqor check tell you whether your agent meets them. Use policy checks as a deployment gate in your CI pipeline, a pre-release verification step, or a local sanity check after a session.
What is a policy check?
critiqor check reads your saved evaluation history and verifies that recent runs meet the reliability thresholds you’ve configured. If every checked run meets the thresholds, the command exits successfully. If any run falls short, the check fails and reports which thresholds were not met.
This makes it straightforward to integrate Critiqor into automated workflows: block a deployment if the trust score is too low, fail a CI job if hallucination risk is above your limit, or enforce consistent standards across a team.
Basic usage
critiqor check reads evaluations from critiqor_evaluations.jsonl in your current working directory. Run this after finalizing one or more sessions to check them against your configured thresholds. To read from a different file, pass the --evaluations flag:
Setting thresholds
Pass threshold flags to define the reliability bar your runs must meet:
You can use either flag independently or combine them. All specified thresholds must be met for the check to pass.
Filtering by agent
If your evaluation file contains runs from multiple agents, use--agent-id to scope the check to a specific agent:
Using a policy file
Instead of passing flags on every invocation, define your thresholds in a policy file and reference it with--policy. This is the recommended approach for teams and CI environments — thresholds live in version control alongside your agent configuration.
policy.json file in your project with your thresholds:
Exit codes
critiqor check uses standard exit codes, making it straightforward to integrate into any CI or scripting environment:
When a check fails, the command prints a summary of which runs failed and which thresholds were not met. Use this output to identify which session to investigate in the dashboard.
Example CI integration (GitHub Actions):