Cairn
NousResearch/hermes-agent

Cron run history missing unified-runtime session lookups

Cluster 138812 · cron. Data as of

Nothing open on GitHub. Fix merged in #139273 on 15 Oct 2026. Check it covers your case.

The short answer

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

These members concern cron runs on the unified runtime, which use local-* session ids while run history appears to look for cron_{job_id}_* sessions, leaving desktop run rows unclickable. Two items are fixes (listing or finding those runs, including via scheduler admission) and one is the bug report; their resolution status is not stated here.

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.

  • #139273 fix(cron): find unified-runtime cron runs by their scheduler admission

    merged to main

    files: apps/desktop/src/app/chat/sidebar/cron-jobs-section.tsx, apps/desktop/src/app/cron/index.tsx, apps/desktop/src/app/cron/open-cron-run.test.ts, apps/desktop/src/app/cron/open-cron-run.ts, apps/desktop/src/app/session/hooks/use-prompt-actions/submit.ts, gateway/session_cron.py, hermes_cli/web_routers/cron.py, hermes_cli/web_routers/sessions.py, hermes_state_common.py, hermes_state_keys.py, hermes_state_media.py, hermes_state_portability.py, tests/fakes/cron_owner.py, tests/hermes_cli/test_cron_run_history_sessions.py, tests/hermes_state/test_cron_run_sessions.py, tests/hermes_state/test_hermes_state.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #138821 fix(cron): list unified runtime run sessions · superseded by another PR → #139273, #134889
  • #138968 fix(cron): find unified-runtime cron runs by their scheduler admission · done elsewhere → #139273, #139268
Closed issues · 1
  • Closed#138812[Bug]: agent cron runs on the unified runtime get local-* session ids; run history still scans cron_{job_id}_* so the desktop run rows become unclickable
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
Merged PRs
#139273
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
15 Oct 2026

For your agent

The same facts, typed.

cluster/138812.json
cluster/138812.md