Cairn

Cron job session reuse and history pruning

NousResearch/hermes-agent · cluster 88268 · 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 items address a bug where each cron job execution creates a new session row instead of reusing a stable per-job session. Related fixes cover using a consistent session key per job and bounding the stored run history.

Open issues1

  • Issue#88268[BUG] Each cron execution spawns a NEW session row instead of reusing a per-job session

Open PRs3

  • PR#88312fix(cron): reuse latest session for each cron job
  • PR#88329fix(cron): use stable session key per job instead of timestamped key
  • PR#88331fix(cron): bound per-job run history — prune old run sessions after each fire
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/88268.json
cluster/88268.md