Cairn
NousResearch/hermes-agent

Cron continuity injects wrong content bug

Cluster 101623 · cron. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These issues and fixes concern a bug where the cron --continuity flag incorrectly injects the previous full run file rather than just the previous response, causing prompts to nest and responses to be truncated on each run.

Open issues1

  • Issue#101623cron: --continuity injects the previous output file prompt-first, so the previous response is truncated away and prompts nest every run

Open PRs1

  • PR#101848fix(cron): inject previous response for continuity

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #102217 fix(cron): continuity injects the previous response, not the whole run file · superseded by another PR → #42262
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
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/101623.json
cluster/101623.md