model-routinglisted

# Model Routing Choose providers from live gateway capability data, not a static claim that one model is universally best. Send every request, including reviews, through the local gtwy stdio MCP server. Do not invoke a provider CLI directly to bypass the gateway's request, session, and audit surfaces. ## Discover Before Selecting 1. Call provider_tool_capabilities through gtwy for current request surfaces, transports, local configuration, and provider-owned tool availability. 2. Call cli_versions when a provider behaves differently from its recorded contract. 3. Omit model unless the user explicitly named a model. If an explicit model is needed, use list_models for the target provider first. 4. Record why a provider is selected: task scope, required capabilities, target repository access, and safety posture. The gateway's CLI provider roster is: | Provider | Gateway request surface | Selection notes | | -------- | ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | Claude | claude_request and claude_request_async | The only provider that can use mcp_managed. | | Codex