Cairn

Cron job output visibility in agent sessions

NousResearch/hermes-agent · cluster 2704 · apps/desktop

Data as of

6 open items. Fix attempted, not merged.

The short answer

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

These issues and PRs concern making cron job results and scheduled outputs observable within the agent's conversational session and memory, so the agent can reference or act on what its own scheduled jobs produced. A related thread covers injecting messages into live gateway/bridge sessions.

Open issues6

  • Issue#5712[Feature]: True Autonomy - Automatically Inject Cron Results into Live Gateway Chat Sessions
  • Issue#8793[Feature]: Synchronize Cron Job outputs into interactive session history for seamless context-aware follow-ups
  • Issue#24246Cron delivery knowledge gap: agent cannot see messages sent to user
  • Issue#37070Agent has no awareness of information delivered by its own cron jobs
  • Issue#50987Feature: optionally record cron/proactive deliveries into the live conversation session
  • Issue#52073When opening the Hermes TUI (desktop app), the agent cannot proactively speak

Open PRs0

No open pull requests.

4 PRs closed without merging

From the close comments: PR volume cleanup 1 · done elsewhere 1 · merged via another change 1 · other 1

  • #2733 feat(cron): log execution results to memories/cron_log.md · PR volume cleanup
  • #4696 feat(cron): write execution summary to agent memory after job completion · other
  • #5659 feat: conversational cron delivery — inject scheduled output into agent session · done elsewhere → b693bee, #2990
  • #7400 feat(cron): add opt-in session history delivery · merged via another change
Closed issues · 3
  • Closed#2704feat: cron job execution results should be written back to conversational memory
  • Closed#2990feat: conversational cron delivery - trigger agent response from scheduled jobs
  • Closed#4595[Feature Request]: Cron Job Results Should Be Observable and Interactable by the Main Agent Session
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.12: 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
apps/desktop
Closed issues
3
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/2704.json
cluster/2704.md