Cairn
NousResearch/hermes-agent

Cron delivery mirroring stored as wrong turn type

Cluster 118863 · cron. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs 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 0 PRs.

A bug caused cron delivery mirror messages to be persisted as user turns rather than assistant turns, affecting how the agent interpreted turn context. The members address identifying and fixing this incorrect turn attribution in cron delivery handling.

Open issues1

  • Issue#118863[Bug]: cron delivery mirror stores the delivery as a user turn, so the agent answers the human as the job's operator

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: stale or abandoned 1 · other 1

  • #118867 fix(cron): persist mirrored deliveries as assistant turns · stale or abandoned → #118863, #2313, #2221, #136816
  • #118899 fix(gateway): exclude cron mirror user turns from turn context · other
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
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/118863.json
cluster/118863.md