Per-cron-job reasoning effort override support
Cluster 23524 · cron. Data as of
2 open items. Fix merged in #91244 on 21 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 6 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #91244. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 0 issues and 2 PRs.
These issues and pull requests concern adding the ability to configure reasoning effort overrides on a per-cron-job basis, including operator-level and per-job granularity across multiple surfaces.
Open issues0
Open PRs2
Fixes on record
-
#91244 feat(cron): jobs can pin their own reasoning effort — CLI-only, kept off the model tool schema (salvage #91038)
files:
cron/jobs.py,cron/scheduler.py,hermes_cli/cron.py,hermes_cli/subcommands/cron.py,tests/cron/test_cron_reasoning_effort.py,tools/cronjob_tools.py,website/docs/reference/cli-commands.md,website/docs/user-guide/features/cron.md
2 PRs closed without merging
From the close comments: done elsewhere 1 · duplicate 1
Closed issues · 1
- Closed#23524Feature: support per-cron reasoning effort overrides
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.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- cron
- Merged PRs
- #91244
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 21 Aug 2026