Teknium
f7d90c9410
The #89503/#70058/#74295/#87279 bug class kept regenerating because every transport and provider profile hand-rolled its own effort translation map (9 sites, 4 distinct policies). New agent/reasoning_effort.py is the single source of truth: - EFFORT_LADDER: canonical low->high ordering (superset check against VALID_REASONING_EFFORTS pinned by test) - clamp_effort(): one policy — supported passes verbatim, otherwise nearest WEAKER supported level (never escalate, never invert the ladder), floor when nothing weaker, 'none' never a degradation target, declared vendor-documented overrides win, bespoke names pass through - declared wire vocabularies as data: OpenAI-compat, Codex Responses, xAI (4.6/legacy), Actual relays, Kimi K3/K2, TokenHub, GLM-5.2, DeepSeek V4, Ollama Cloud, Meta, Solar Converted sites (all behavior-preserving except noted): - chat_completions chokepoint, Kimi + TokenHub paths - codex transport (backend branches now pick a declared set) - auxiliary_client Responses path - hermes_cli.models clamp_reasoning_effort_to_supported -> thin wrapper - plugins: kimi-coding, zai, opencode-zen, deepseek, ollama-cloud, meta-ai, upstage, custom (copilot already routes via the wrapper) Behavior fixes the shared policy surfaces: - ollama-cloud/opencode-go 'minimal' now degrades to 'low' instead of being dropped (drop left the server default = MORE thinking than asked) New tests: ladder contract (every configurable level is clamped by every declared wire set; monotonicity across the full ladder for every set).
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.