NousResearch/hermes-agent

Cron scheduler missing per-job max_tokens wiring

Cluster 58423. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

A bug report and multiple fix attempts address the cron scheduler failing to read per-job max_tokens from job config and pass it to the AIAgent constructor. Members share a single focused theme around this missing parameter propagation.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1 · other 1

  • #58440 fix(cron): read per-job max_tokens from job config and pass to AIAgent · other → #58431, #58378, #58397
  • #58582 fix(cron): wire max_tokens from per-job config into AIAgent constructor · duplicate → #58440, #58423
  • #61149 fix(cron): honor per-job max tokens · done elsewhere → #58582
Closed issues · 1
  • Closed#58423[Bug] cron scheduler.py run_job() never reads per-job max_tokens — AIAgent() always gets None
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.50: 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

Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.