Understand the work
Complexity, recent tool context, code, security, and other risk signals can keep the requested model in place.
CutCtx routing is opt-in. It keeps the requested model when the work is high-risk, ambiguous, tool-heavy, capability-incompatible, or not proven safe for the active provider, account, and transport.
Conservative by default · Observable decision reasons · No silent provider switch
CutCtx does not treat a short prompt as automatically safe to downgrade. The request, available target, and transport must all satisfy the policy before a route can apply.
Complexity, recent tool context, code, security, and other risk signals can keep the requested model in place.
Tool calling, structured output, vision, audio, streaming, and other required capabilities must be supported by the target.
Provider, account, and transport proof constrain which targets can be considered.
Readiness, certification, availability, and cost gates keep unknown or unsuitable candidates out.
A route applies only when every gate passes. Otherwise, the requested model retained outcome is the correct result.
Routing evidence identifies an applied source-to-target pair or a clear retention reason such as no route, insufficient confidence, unsuitable workload, or missing capabilities.
Only after complexity, capability, provider, account, transport, readiness, and certification gates pass.
Used when a route is not warranted; no fallback is used to bypass a rejected safety condition.
Examples include no_route_for_model, confidence_below_threshold, and workload_not_downgradeable.
The primary named preset for the documented conservative routing behavior.
Compatibility aliases, not separate products or routing plans.
Routing status is read-only. It does not silently change providers, accounts, credentials, transports, or models.
Install locally, wrap a supported workflow, and inspect routing status alongside your own savings evidence.