Conversation Continuity
The active conversation strategy is STICKY: it keeps the model chosen for a conversation to preserve continuity. PASSTHROUGH exists in the stored mode vocabulary but cannot currently be activated; ADAPTIVE is not an available mode. There is no supported mode-switching recipe here.
A later prompt's classification does not guarantee a different model for an existing conversation. Review the model used in Request Logs. The model's context limit still applies; bound conversation history and handle upstream context-window errors.
Routing stays within the provider selected by the proxy path. It evaluates applicable customer rules before global defaults, with lower priority numbers evaluated first. The global low-confidence guard can preserve the requested model. Capabilities, request shape and STICKY conversation continuity can prevent a change. A successful request can have Makas-Was-Routed: false and zero savings.