Cairn
NousResearch/hermes-agent

Cron jobs not receiving model api_key/base_url config

Cluster 32239 · cron. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

All three members concern the cron scheduler not passing runtime provider settings, specifically model.api_key and model.base_url from config.yaml, into resolve_runtime_provider for scheduled jobs. One appears to be an issue report and the other two are fix-titled pull requests; their outcomes are not stated in the titles.

Open issues0

No open issues.

Open PRs1

  • PR#46853fix(cron): propagate runtime provider config to scheduled jobs

1 PR closed without merging

From the close comments: stale or abandoned 1

  • #32256 fix(cron): propagate model.api_key / model.base_url from config.yaml to resolve_runtime_provider · stale or abandoned
Closed issues · 1
  • Closed#32239Cron scheduler doesn't propagate model.api_key / model.base_url from config.yaml to resolve_runtime_provider()
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: 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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/32239.json
cluster/32239.md