Cairn
NousResearch/hermes-agent

Cron jobs: pass target_model to resolve_runtime_provider

Cluster 45245 · cron. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
10items grouped
Known?
Yes. 10 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 6 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

Most members concern scheduled cron jobs not passing target_model when resolving the runtime provider, tied to reported base_url mismatch and HTTP 401 errors with certain model routing. One member, about counting skills in profiles, appears unrelated.

Open issues1

  • Issue#45245Cron scheduler omits target_model when resolving runtime provider — same root cause as #18586

Open PRs2

  • PR#46853fix(cron): propagate runtime provider config to scheduled jobs
  • PR#68403fix(profiles): count global + external skills in _count_skills

6 PRs closed without merging

From the close comments: done elsewhere 2 · duplicate 2 · superseded by another PR 2

  • #45244 fix(cron): pass target_model to resolve_runtime_provider · superseded by another PR → #78427
  • #45248 fix(cron): pass target_model to resolve_runtime_provider for pinned-model jobs · duplicate → #45244
  • #45294 fix(cron): pass target_model to resolve_runtime_provider in run_job · duplicate → #45244
  • #45338 fix(cron): pass target_model to resolve_runtime_provider (#45245) · superseded by another PR → #45244, #45245
  • #68763 fix(cron): pass target_model to resolve_runtime_provider to prevent base_url mismatch · done elsewhere → 786df3c
Show 1 more
  • #68846 fix(cron): pass target_model to resolve_runtime_provider to prevent base_url mismatch · done elsewhere → 786df3c, #68403
Closed issues · 1
  • Closed#68762Cron jobs fail with HTTP 401 when config.yaml model.default is switched to an anthropic_messages-routed model (e.g. qwen on opencode-go)
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.19: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
cron
Closed issues
1
Attempts
6 PRs closed without merging

For your agent

The same facts, typed.

cluster/45245.json
cluster/45245.md