Cairn

Cron repeat logic and clarify answer preservation fixes

NousResearch/hermes-agent · cluster 106077

Data as of

Nothing open on GitHub. Fix merged in #106532. Check it covers your case.

The short answer

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

Two distinct bug fixes: one corrects cron schedule repeat behavior when the schedule kind changes, and another ensures batch clarify answers are not dropped during compression or summarization passes.

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.

  • #106532 Cron schedule changed from one-shot to recurring keeps firing instead of retiring after one run (#106096, salvage #106106)

    merged to main

    files: cron/jobs.py, tests/cron/test_jobs.py

  • #106533 Compaction keeps batch clarify answers for the summarizer (#106077, salvage #106089)

    merged to main

    files: agent/context_compressor.py, contributors/emails/[redacted:email], tests/agent/test_context_compressor.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #106089 fix(compression): preserve batch clarify answers in summarize pass · merged via another change → 3026f4a, #106533
  • #106174 fix(cron): re-derive repeat default when schedule kind changes (#106096) · done elsewhere → ae65399, #106532, #106106, #106077, #106089, #106533
Closed issues · 1
  • Closed#106077Compression drops clarify answers before summarization, losing decision and permission context
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.40: 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
#106532, #106533
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
9 Sep 2026

For your agent

The same facts, typed.

cluster/106077.json
cluster/106077.md