[FEATURE]: Router presets — named, switchable configurations for multi-provider routers (OmniRoute, OpenRouter, LiteLLM, 9Router) #34711

Feature Request: Named, switchable router presets

Problem

When using OpenCode with multi-provider routing (OmniRoute, OpenRouter, LiteLLM, 9Router), users must manually reconfigure the \\provider\\ / \\model\\ settings each time they want to switch routing strategies. For example:

• Cost routing: cheap models for drafting, expensive for review
• Reliability routing: failover chain (Bedrock → Together → OpenRouter)
• Offline routing: local Ollama only, no cloud calls
• Experimental routing: latest preview models, accept breakage

Currently there is no way to save these configurations as named presets and switch between them without editing the config file.

Proposed behavior

Add a \
outer.presets\\ section to the OpenCode config (JSONC or similar) that lets users define named routing configurations:

\\jsonc
{
"router": {
"activePreset": "cost",
"presets": {
"cost": {
"provider": "omniroute",
"model": "auto",
"baseUrl": "http://localhost:20128/v1"
},
"local": {
"provider": "ollama",
"model": "llama3.1:8b",
"baseUrl": "http://localhost:11434/v1"
},
"reliable": {
"provider": "anthropic",
"model": "claude-opus-latest"
}
}
}
}
\\

Switching presets via slash command: \/preset cost\\ or \/preset local\\

Why

Multi-provider router setups are common in fleet-style agent workflows. Switching routing strategy mid-session (e.g., switching to local when offline, or to a high-capacity router for a long refactor) requires editing config files and restarting. Named presets would make this a one-command operation.

Environment

• OpenCode CLI on Windows 11 Enterprise
• Using OmniRoute (localhost:20128) as primary router