The chat_completions chokepoint fix (ultra->max for every model, cherry-picked from #89509) has siblings with the same bug shape: - codex.py: ultra->max was gated on gpt-5.6 only; now baseline for all Responses-API models (backend-specific branches still override). - Kimi top-level reasoning_effort: K3 accepts low/high/max only — 'medium' and upper-ladder levels were dropped to the medium default (400s on K3, ladder inversion on K2). Full ladder mapped per family, mirroring the kimi-coding plugin's K3 map. - TokenHub: 'minimal' fell through to the 'high' default (asked least, got most); full ladder now mapped onto low/medium/high. - auxiliary_client Responses path: ultra->max alongside the existing minimal->low clamp. - custom provider plugin: ultra capped at max instead of forwarded verbatim to GLM/vLLM/SGLang backends that reject it. - copilot plugin: ad-hoc downgrade rules replaced with the shared clamp_reasoning_effort_to_supported ladder walk so ultra/max resolve to the strongest supported level instead of medium (#74295). Sabotage-verified: new sibling-site tests fail 6/10 without the fixes.
Model Provider Plugins
Each subdirectory is a self-contained provider profile plugin. The
directory layout mirrors plugins/platforms/:
plugins/model-providers/
├── openrouter/
│ ├── __init__.py # registers the ProviderProfile
│ └── plugin.yaml # manifest: name, kind, version, description
├── anthropic/
│ ├── __init__.py
│ └── plugin.yaml
└── ...
How discovery works
providers/__init__.py._discover_providers() scans this directory (and
$HERMES_HOME/plugins/model-providers/) the first time anything calls
get_provider_profile() or list_providers(). Each __init__.py is
imported and expected to call providers.register_provider(profile).
User plugins at $HERMES_HOME/plugins/model-providers/<name>/ override
bundled plugins of the same name — last-writer-wins in
register_provider(). Drop a file there to replace a built-in.
Adding a new provider
-
Create
plugins/model-providers/<your_provider>/__init__.py:from providers import register_provider from providers.base import ProviderProfile my_provider = ProviderProfile( name="your-provider", aliases=("alias1", "alias2"), display_name="Your Provider", description="One-line description shown in the setup picker", signup_url="https://your-provider.example.com/keys", env_vars=("YOUR_PROVIDER_API_KEY", "YOUR_PROVIDER_BASE_URL"), base_url="https://api.your-provider.example.com/v1", default_aux_model="your-cheap-model", ) register_provider(my_provider) -
Create
plugins/model-providers/<your_provider>/plugin.yaml:name: your-provider-profile kind: model-provider version: 1.0.0 description: Short sentence about the provider author: Your Name
Nothing else needs to change. auth.py, config.py, models.py,
doctor.py, model_metadata.py, runtime_provider.py, and the
chat_completions transport all auto-wire from the registry.
Non-trivial profiles
Override the ProviderProfile hooks in a subclass for per-provider
quirks — see plugins/model-providers/openrouter/__init__.py for
build_extra_body and build_api_kwargs_extras examples, and
plugins/model-providers/gemini/__init__.py for thinking_config
translation.