NousResearch/hermes-agent

Cron run history scoped to wrong profile

Cluster 115345. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #117025 on 20 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #117025. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #117025. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #117025, then check it covers your case.

Read #117025 Pick up a Lab task

A bug where desktop cron run history is read from the active profile rather than the job's owning profile, causing non-owner jobs to always show no run history. Related fixes address reading history from the correct owning profile in a cross-profile job list.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#117025 fix(cron): Desktop cron run history and per-job actions follow the job's owning profile across the cross-profile list (#115345, salvage #115388)

merged to main

files: hermes_cli/web_routers/cron.py, tests/hermes_cli/test_web_server_cron_profiles.py, website/docs/user-guide/desktop.md

1 PR closed without merging

From the close comments: merged via another change 1

#115388 fix(cron): read a job's run history from its owning profile · merged via another change → b5c0bd6, #117025, #115345, #115388

Closed issues · 1

Closed#115345[Bug]: Desktop cron run history is scoped to the active profile while the job list is cross-profile — non-owner jobs always show "No runs yet"; maintainer decision requested on list scope

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

Merged PRs: #117025
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 20 Sep 2026

For your agent

The same facts, typed.

cluster/115345.json
cluster/115345.md