mirrors/hermes-agent
1
0
Fork 0
mirror of https://github.com/NousResearch/hermes-agent.git synced 2026-07-20 15:33:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 6

refactor(reasoning): unify per-model reasoning resolution behind a single chokepoint

Browse source 
Collapse the six per-surface copies of override-then-global resolution
(CLI startup, gateway, TUI, cron, /model switch, fallback activation)
onto one shared resolve_reasoning_config() in hermes_constants.

Also fixes the gateway resolving reasoning against config model.default
instead of the session's effective model: after a session-only /model
switch, the switched model's override now applies (gateway message paths
pass the resolved session model through _resolve_session_reasoning_config;
/reasoning status reads the session model override).

Cleanup: drop docs/PER_MODEL_REASONING.md (duplicates the website docs
page), drop the change-detector _config_version test (no bump needed —
deep-merge handles new keys), remove a stale plan-reference comment.

Adds chokepoint contract tests (13) and gateway session-effective-model
regression tests (2).
This commit is contained in:
Teknium 2026-07-14 07:16:54 -07:00
parent d9cdb81923
commit e81d18dfb4
11 changed files with 302 additions and 253 deletions
Download patch file Download diff file Expand all files Collapse all files

101
docs/PER_MODEL_REASONING.md
View file

@ -1,101 +0,0 @@
# Hermes Agent Configuration Guide
## Per-Model Reasoning Effort Overrides
You can configure different reasoning effort levels for different models. This allows you to set `high` effort for complex reasoning models like `claude-opus-4.5` while keeping `medium` for faster models like `gemini-flash`.
### Configuration
Edit your `config.yaml` (typically at `~/.hermes/config.yaml`):
```yaml
agent:
reasoning_overrides:
claude-opus-4.5: high
gemini-flash: medium
gpt-4.5: high
```
### Key Matching
The model name matching is **spelling-tolerant**. All of these variations will match:
- `claude-opus-4.5`, `claude-opus-4-5`, `claude-opus.4.5`
- `anthropic/claude-opus-4.5`, `openrouter/anthropic/claude-opus-4.5`
- With or without provider prefixes
Exact matches take precedence over variants.
### Resolution Order
When determining reasoning effort for a model, Hermes checks in this order:
1. **Session override**: `/reasoning high` (current session only)
2. **Per-model override**: `agent.reasoning_overrides.<model>` from config.yaml
3. **Global default**: `agent.reasoning_effort` from config.yaml
### How It Works
The override applies automatically in these scenarios:
- **CLI startup**: Uses the override for the configured default model
- **Gateway messaging**: Each gateway session uses the override for its model
- **Desktop/TUI**: Uses the override for the configured model
- **Model switching**: When you switch models, the reasoning effort updates to the new model's override
- **Fallback activation**: When the primary model fails and Hermes falls back to a secondary model, it uses that fallback model's override
- **Reasoning recovery**: When the primary model recovers after a fallback, the original model's override is restored
### Examples
#### Example 1: High effort for Opus, medium for others
```yaml
agent:
reasoning_overrides:
claude-opus-4.5: high
```
#### Example 2: Different efforts per model
```yaml
agent:
reasoning_overrides:
claude-opus-4.5: high
gemini-2.0-flash: low
gpt-4.5: high
o3-mini: medium
```
#### Example 3: With provider prefixes
```yaml
agent:
reasoning_overrides:
anthropic/claude-opus-4.5: high
google/gemini-2.0-flash: low
```
All of these are equivalent — the provider prefix is optional.
### Disabling Reasoning for Specific Models
Set the override to `none` to disable reasoning for a specific model:
```yaml
agent:
reasoning_overrides:
gemini-flash: none
```
### Troubleshooting
**Override not taking effect?**
- Check the exact model name in your config with `/model`
- Verify the override is under `agent.reasoning_overrides` (not `agent.reasoning_effort`)
- Restart the gateway or CLI session after editing config.yaml
- Check logs for parsing errors
**Override applies but reasoning doesn't work?**
- Not all models support reasoning (e.g., `gemini-flash` has limited support)
- Check the model's documentation for reasoning capability
- Use a model that explicitly supports extended thinking
**Session override not respecting per-model override?**
- Session overrides take precedence (by design)
- Clear the session override with `/reasoning default` to return to the per-model override