Model Execution Engine

Critique routes different model roles for different jobs. Automated PR review and Remedy share a curated runtime catalog; Critique Chat uses a broader chat catalog tuned for conversation.

Runtime roles (review & Remedy)

Chat does not use the review runtime role list — pick chat models in Settings.

Plans and the catalog

Models are tagged with a minimum plan (Standard, Pro, or Ultra). Your installation’s plan determines which model IDs appear in policy dropdowns and whether a requested override is allowed.

The live catalog changes as providers ship new versions. The Models page and dashboard pickers are authoritative; documentation lists concepts, not every model id string.

Credit floors

Every review-capable model has a credit floor — the minimum remaining balance Critique expects before starting work with that model. Floors scale with capability: frontier models require more headroom than fast economical models.

Floors work together with Billing & credits so one run cannot silently exhaust a month on a single PR.

Fallbacks

If a primary model is unavailable, Critique may route to a configured fallback and record that in run telemetry. You see the effective model on the review run detail page, not necessarily the policy default.

OpenRouter and BYOK

Many deployments call models through OpenRouter. Teams can optionally supply their own OpenRouter key; billing and credit gates then follow BYOK and Billing & credits.

Practical guidance for admins

• Set repository policy defaults at installation level; override only where needed.
• Match plan tier to the models you select in policy — Ultra models on a Standard plan will not run.
• Use Usage to see which models actually drove spend after the first month.

For policy fields that reference models, see Policy fields.