Cairn

Cron job per-job output token cap feature

NousResearch/hermes-agent · cluster 131119 · cron

Data as of

4 open items. Fix attempted, not merged.

The short answer

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

These issues and PRs relate to adding support for a per-job maximum output token limit in the cron scheduler, including a new --max-tokens flag at job creation and honoring a max_tokens field in jobs.json.

Open issues1

  • Issue#131119cron: per-job max_tokens (create --max-tokens + jobs.json field honored by scheduler)

Open PRs3

  • PR#131136feat(cron): support per-job output token caps
  • PR#131139fix(cron): cap scheduled agent output tokens
  • PR#131140feat(cron): per-job max_tokens caps the output tokens a job's turn requests
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

Subsystem
cron
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/131119.json
cluster/131119.md