How Routing Works
PrettiFlow decides which model to use based on what kind of task it's doing. You don't configure this — it happens automatically on every request.
Task-based routing
Tasks fall into two broad groups:
Decision tasks
Execution tasks
Automatic fallback
If the preferred provider for a task isn't available, PrettiFlow cascades to the next option automatically — so a single provider outage doesn't block your build.
Pick the best-fit model
Based on the task type, PrettiFlow selects a preferred model.
Check availability
If that provider is configured and reachable, it's used.
Fall back if needed
Otherwise PrettiFlow moves to the next provider in line, keeping your build running.
Safety checks
Before running potentially risky operations (like shell commands), a separate lightweight "judge" model reviews the action first. This guardrail runs independently of the model doing the main work.