fix(curator): honor curator.auxiliary.{provider,model} override (#17572) - #17781
Closed
yonefive71 wants to merge 1 commit into
Closed
fix(curator): honor curator.auxiliary.{provider,model} override (#17572)#17781yonefive71 wants to merge 1 commit into
yonefive71 wants to merge 1 commit into
Conversation
The curator's _run_llm_review() resolved provider+model exclusively
from cfg['model'], silently ignoring the documented
curator.auxiliary.{provider,model} schema (config.py:950-955).
As a result the curator always ran on the user's main model — for
Opus users this means weekly runs on the most expensive model when
the whole point of an auxiliary slot is to pin a cheaper one.
This patch reads curator.auxiliary first and falls back to the main
model fields when either side is null, matching the schema comment
('Leave null to use Hermes' main auxiliary client resolution').
Provider and model can be overridden independently.
Tests cover three cases:
- auxiliary unset → main model (current behavior preserved)
- both fields set → aux wins
- partial override (provider only) → main model retained
Fixes NousResearch#17572
Collaborator
Collaborator
|
Likely duplicate of #17584. |
Contributor
|
Thanks @yonefive71 — superseded by PR #17868 (merged on main as 0da968e), which fixes #17572 by unifying curator config under |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #17572. The curator's
_run_llm_review()resolved provider and model exclusively fromcfg["model"], silently ignoring thecurator.auxiliary.{provider, model}schema documented inhermes_cli/config.py:950-955. As a result the curator always ran on the user's main model — for Opus users this means weekly runs on the most expensive model when the whole point of an auxiliary slot is to pin a cheaper one.The bug
agent/curator.py:761-763(before this patch):No reference to
cfg["curator"]["auxiliary"]anywhere in the resolution path, even though the default config block reserves it:Fix
Read
curator.auxiliaryfirst and fall back to the main model fields when either side is null. Provider and model can be overridden independently (provider-only override keeps the main model, and vice versa).Tests
Three new cases in
tests/agent/test_curator.py:auxiliaryunset → main model (current behavior preserved)pytest tests/agent/test_curator.py→ 34 passed.Notes
resolve_runtime_provider()is still called with the resolved provider+model, so credential pool / OAuth / pool-backed flows continue to work for the aux model.auxiliaryblock has been inDEFAULT_CONFIGfor a while; this just wires it up.