Cron context missing from active-turn redirects

NousResearch/hermes-agent · cluster 107856 · cron

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 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 2 PRs.

These items address a bug where cron context attached to a session was not being carried through active Discord redirects or active follow-up requests. The fixes aim to preserve and include that context during those flows.

Open issues1

  • Issue#107856[Bug]: Active Discord redirects miss cron context already attached to the same session

Open PRs2

  • PR#107862fix(gateway): include opted-in cron context in active-turn redirects
  • PR#107931fix(cron): preserve delivered context for active follow-ups
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
0 PRs closed without merging

For your agent

The same facts, typed.